Visual Studio 2017 (non-programming) problem
-
Try Again sorry. I have not tried 2017 yet, I have always had issues with debug mode until I set devenv.exe to launch as admin https://docs.microsoft.com/en-us/visualstudio/ide/user-permissions-and-visual-studio?view=vs-2015 https://docs.microsoft.com/en-us/visualstudio/ide/user-permissions-and-visual-studio?view=vs-2015[^] need coffee..
Toto1107
-
No, just as normal user. I have not actually tried it as administrator, but since the problem is so random it is difficult to reproduce at will.
I recommend you always run VS 2017 "as administrator". You may find some of your occasional issues disappear.
-
Sometimes I build first, and then use F5. At other times I just use F5. In both cases the build either completes (sometimes with errors) or the hang occurs. I have not seen it with a different project, but I am building this one quite frequently.
I'd keep Task Manager open and watch the "profile" of your session and see if there is a pattern for that particular project: all kinds of stuff runs under VS; including JavaScript. Your browsers are also competing for memory: a "window" (process) for each Tab. Each (my) VS session and each browser can easily consume over 1 GB.
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
MS employee here. I unfortunately have no connection to the VS team and am not an avid developer myself, but if you'd like a code for a free support case please let me know, I'd be happy to help get you rolling forward. -- Jon
-
Try Again sorry. I have not tried 2017 yet, I have always had issues with debug mode until I set devenv.exe to launch as admin https://docs.microsoft.com/en-us/visualstudio/ide/user-permissions-and-visual-studio?view=vs-2015 https://docs.microsoft.com/en-us/visualstudio/ide/user-permissions-and-visual-studio?view=vs-2015[^] need coffee..
Toto1107
-
I recommend you always run VS 2017 "as administrator". You may find some of your occasional issues disappear.
-
I'd keep Task Manager open and watch the "profile" of your session and see if there is a pattern for that particular project: all kinds of stuff runs under VS; including JavaScript. Your browsers are also competing for memory: a "window" (process) for each Tab. Each (my) VS session and each browser can easily consume over 1 GB.
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
I have had a number of occasions recently when building a project*, that VS stops and kills Windows completely. The mouse cursor disappears, the text caret stops flashing and even Ctrl-Alt-Del does not work. The only way to get out of it is to power off and on again. *I think it only happens when I press F5 to build and debug. And the code itself is not exactly complicated. Anyone else had this?
-
This is a stretch, but when I am having weird system problems I sometimes go to event viewer and look at Windows Logs --> System Logs. Disk errors and other ephemera may show up around the time you had the Visual Studio problems.
-
This is a stretch, but when I am having weird system problems I sometimes go to event viewer and look at Windows Logs --> System Logs. Disk errors and other ephemera may show up around the time you had the Visual Studio problems.
-
I have had a number of occasions recently when building a project*, that VS stops and kills Windows completely. The mouse cursor disappears, the text caret stops flashing and even Ctrl-Alt-Del does not work. The only way to get out of it is to power off and on again. *I think it only happens when I press F5 to build and debug. And the code itself is not exactly complicated. Anyone else had this?
We have had Visual Studio crash on us. For most, we found that disabling the source control plugin and/or deleting the intellisense file helped. You could try running VS in safe mode to see if the problem still happens (devenv.exe /SafeMode) or you could try looking at suppressed alert messages to see if that gives you any more information (devenv.exe /ResetSkipPkgs).
-
We have had Visual Studio crash on us. For most, we found that disabling the source control plugin and/or deleting the intellisense file helped. You could try running VS in safe mode to see if the problem still happens (devenv.exe /SafeMode) or you could try looking at suppressed alert messages to see if that gives you any more information (devenv.exe /ResetSkipPkgs).
-
Have a look at the hardware.These have a spike on "F5" -HDD/SSD (bad sectors, a lot of writing happening) -Memory (any issue can freeze the OS) -Graphics card (some drivers don't really fancy VS) disable graphics acceleration on VS It could also be the AV. Some other options :-D - use notepad and command line compile - use a hammer/basebal bat and fix the machine
Paulo Gomes Measuring programming progress by lines of code is like measuring aircraft building progress by weight. —Bill Gates Everything should be made as simple as possible, but not simpler. —Albert Einstein
I was thinking similarly: - memory. Run intensive memory tests overnight. Someone posted tips elsewhere. If they don't run for hours you aren't testing thoroughly enough. - thermal problems. there are various apps that monitor your systems thermal sensors. Check what temperatures you are running. - HD/SSD - can you check SMART status? Check the event logs for IO errors Try going to build settings to only allow a single build at a time. This will reduce system load quite a bit, though of course the builds will take longer. It would be interesting to see if it makes a difference. If it does I'd say it points to one of the problems above, or some similar physical issue with the machine. Good luck.
-
I have had a number of occasions recently when building a project*, that VS stops and kills Windows completely. The mouse cursor disappears, the text caret stops flashing and even Ctrl-Alt-Del does not work. The only way to get out of it is to power off and on again. *I think it only happens when I press F5 to build and debug. And the code itself is not exactly complicated. Anyone else had this?
At one time the members of my development team would see a symptom like this when pressing F5 to debug. In our case, we had some security software that IT required us to install. I think it was called FireAMP or something like that. Since we saw the issue start right after that was deployed, we requested permission to disable it, and that seemed to solve the issue.