|
That has to be one of the coolest stories I've read.
For a minute I thought this was leading into the machine overheating, and he opened the window to allow it to cool down. Overheating was a very common problem, and still is. But the light on the photocells is waaayyy better.
|
|
|
|
|
Slacker007 wrote: try staring VS as admin
I've been staring at VS all day, it just stares back at me...
|
|
|
|
|
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
- 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.
|
|
|
|
|
Try running the same project/solution from VS but on another PC, if no problems happen, then there is something wronge in one of your computer components that make VS hang.
Remember that VS uses: HDD+RAM+CPU+GPU+LAN Controllers, to name a few, so if any one of the components have a problem, it might affect VS.
I forgot:
Sometimes the browsers (Chrome/firefox) get entangled with VS by a way or another.
Hope for you the best.
___________________________________________
May god give u good health and knowledge.
modified 24-Sep-18 4:32am.
|
|
|
|
|
Make a flash drive that boots to the memtest86 (or whatever it's called) and let it test your RAM for a while. I've seen quite a few funky PCs fail this test, replace the memory, and problems all gone.
|
|
|
|
|
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".
|
|
|
|
|