After running my code again after two weeks time, my code suddenly runs more than twice as slow.
On GitLab I reverted to earlier commits and where those projects used to run at 3500ms the same process now takes over 8000ms.
Updating Visual Studio 2019 to version 16.11.5 did not solve the problem, nor did repairing Visual Studio, cleaning up my computer, updating Windows, or restarting. The problem exists both in Debug mode and Release mode.
Did anyone ever experience similar problems with Visual Studio and found the cause?
Related
I am using Visual Studio 2019, version 16.60 for game development with c++ and just since yesterday, it has suddenly started reporting thousands of errors.
Tried deleting the .suo file in the .vs folder, restarted Visual Studio, restarted the system but no good.
Also tried uninstalling and reinstalling Visual studio and still no change .
I hope someone can solve this as this is becoming extremely frustrating to find my actual errors in the code amidst all the mess.
I have the problem that I cannot update or install Visual Studio anymore on my system.
Today I saw that a newer Visual Studio 2017 version was released and I tried to start the VS installer for the update process. The start for the installer was just spinning but nothing happened. After that I tried to start the installer separately from VS but it didn't work either.
So I continued to make an even bigger mistake by assuming my installed version is bad and to completely reinstall Visual Studio by uninstalling and then trying to start the normal installation process.
Unfortunately it didn't work.
After downloading the webinstaller, it downloads the installer packages it needs but the vs_installer.exe itself will never run successfully afterwards (also if started manually).
There is no error shown directly. It just does not start. The EventViewer is also not showing any errors I would say have a connection to the problem.
Any ideas? Thanks!
After a bit of communication with the Visual Studio team they pointed me to the only thing they know could cause this issue.
Some time ago I added an environment variable to my system named NODE_OPTIONS. It was necessary because the builds of our Angular applications are so big that we had to adjust the available memory size.
Removing the environment variable enabled me to start vs_installer.exe and to reinstall Visual Studio again.
It's a bit obscure and not many people will have this problem. But I hope Microsoft will fix it anyway.
P.S. The silent crash is caused by the usage of Electron for the Visual Studio installer. The person from Microsoft, who helped me to workaround the problem, told me that they are working on a fix.
Have a very annoying problem, xoreax Incredibuild keeps getting reinstalled when I apply Visual Studio 2017 updates.
I remove it from Add/Remove and it's fine for a week or too, and then Microsoft release yet another visual studio 2017 update, and lo-and-behold, Incredibuild is back and needs manual removal again.
I really don't want this garbage, Visual Studio is slow enough as it is, without even more useless junk being pushed onto me.
I recently made the change to Visual Studio 2015 from Visual Studio 2012 as my compiler for my c++ projects. After making this change I have noticed that visual studio will frequently hang in the build process.
This never occurred with Visual Studio 2012. The hangups are at random points and do not occur at the same build points in my projects.
When I ran VS in administrator mode and got all of the cl.exe's and link.exe's to appear as command prompts I was able to see when they hung. And there were no errors thrown or anything.
The only way I have successfully worked around this issue is by setting Visual Studio's build process to only process one project at a time and use only one compilation simultaneously. However I cant maintain this as my build time is somewhere around 3-4 hours (Yes, this is a HUGE project).
I think this is a duplicate of Visual Studio 2015 Win64 hangs during solution build. I posted an answer there. In short, there may be a patch that resolves the issue:
https://www.microsoft.com/en-us/download/details.aspx?id=51161
I am running Visual Studio 2005 on Windows XP. It crashes without any error, log or trace when I try to load the solution for our product that contains 362 projects. I don't think the size of solution (362) is a problem, because it works on my colleagues computers. There is no entry of this in Event Viewer.
Any help to locate root cause of the problem or any solution if known would be greatly appreciated.
Thanks,
Shashibhushan
Thanks Luke for your suggestion. When I debugged using windbg.exe, it became evident that the exception was being generated at the time of loading dll related to "VMDebugger - Visual Studio Integrated Virtual Machine Debugger". I disabled it from the Add-in Manager and now the solution is being loaded successfully and working fine. Thanks for all your suggestions.
Thanks,
Shashi
Just some general thougts:
Uninstall SP1 - i had several difficulties with it. I.e. i was unable to create a working x64 DLL using SP1
Try again on a different machine that so far does not have Visual Studio on it. So you know wheteher its a problem of the Machine, or maybe a general Problem of Visual Studio
Uninstall and reinstall Visual Studio.
EDIT:
If you started seeing these problems yesterday i would even more strongly suggest, to uninstall and reinstall VisualStudio as well as SP1.
Did you install any new software recently?