|
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
|
|
|
|
|
Thanks Jon, I may get back to you on that. In the meantime I think I need to gather more useful information before opening a bug report.
|
|
|
|
|
|
I, too, have experienced this behavior from Visual Studio for the last few months, both 2015 and 2017. I have yet to find a solution; however, it seems to help when I take the time to reboot the PC every 10 to 12 debug sessions. The trouble is that I tend to get wrapped up in the task at hand, and forget to do the reboots!
I assume that there is something in my PC environment that is causing this, and would love to hear of any solutions anyone out there comes up with.
|
|
|
|
|
Are you running VS 2017 "run as administrator"?
|
|
|
|
|
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.
|
|
|
|
|
I will give it a try but I do not think it's a permissions issue; it actually hangs the system completely so I cannot even get task manager started in order to kill the offending process.
|
|
|
|
|
I'm not convinced F5 / Debug always "builds" enough and winds up trying to execute "out of date" code.
I'm convinced that a "build" + F5 is sometimes needed versus a straight "F5" at certain times.
(My solutions usually involve multiple projects / dll's).
And "cleaning" and "unloading / reloading" a project can also "straighten out" VS when it gets symptomatic.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
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
|
|
|
|
|
Thanks Gerry, I had not thought of that.
|
|
|
|
|
|
That link points to your answer.
|
|
|
|
|
|
I have had that problem with a previous version, but this one is quite different.
|
|
|
|
|
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 meant to write "Windows Logs --> System".
|
|
|
|
|
|
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).
|
|
|
|
|
Thanks, I will try your suggestions also.
|
|
|
|
|
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.
|
|
|
|
|
...QA came to mind.[^]
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
It won't even muffle the sound. QA is a bad bad land.
|
|
|
|
|
It will if you use it to secure their wrists, and then cover the nose and mouth...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|