Last post Jul 02, 2013 12:28 PM by pkpjpm
Apr 05, 2013 02:42 PM|rmdw|LINK
More than any other previous version of Visual Studio, I've noticed that VS2012 hangs quite a bit when I'm debugging my ASP.NET application and want to do something as simple as check the value of a variable.
I've done some research on the subject and all I can find are some suggestions that I need to reinstall Windows and then Visual Studio again. Whatever! How about Microsoft recognize this as a serious bug and take steps to fix it?!?
Apr 05, 2013 04:05 PM|Rion Williams|LINK
I've haven't noticed any issues regarding hanging or any other performance-related issues while debugging with Visual Studio 2012.
Have you downloaded all of the most recent updates for Visual Studio 2012 (and any other important updates that might be available through Window Update)? You should also do the usual checks for viruses etc.
Those would be my primary recommendations, especially before reinstalling Visual Studio or Windows.
Apr 05, 2013 06:29 PM|R.Mani|LINK
Please check out the below link.
Apr 06, 2013 08:56 AM|ramiramilu|LINK
I never observed it to....download VS 2012 Update 2...
Apr 06, 2013 10:08 AM|rmdw|LINK
I thought I had all the updates. I did not. I've now installed VS2012 - Update #2. Hopefully this will help to resolve the problem.
Thank you all for your feedback!
May 03, 2013 07:13 PM|rmdw|LINK
It's now been a month since I added my original post. All of the VS2012 Updates have been applied. Yet VS2012 is still periodically hanging. There's no sense to when or why it happens. I'll add a breakpoint somewhere and then step through my code. It
usually lets me go through a few lines, check a few values and then . . . suddenly it hangs up.
I hope that Microsoft can resolve this with Update 3.
May 31, 2013 11:10 AM|Javed_A|LINK
Just to add my voice to yours, I have the same problem. Before Update 2, the problem was worse, but largely limited to working in xaml in silverlight. Now in Asp, even going from one open window to another can take 10 seconds, and I have only 4 open windows.
I have 18 GB RAM, i7 2.93 GHZ system. The only app open is VS. There is definitely something wrong here.
Jun 02, 2013 10:20 AM|tandori|LINK
After a lot of cussing, I figured out my problem with Visual Studio debug sessions hanging and failing repeatedly...don't know if this helps someone else, but I made the mistake of installing Google Earth. This automatically installed the ASK tool bar,
the bane of my existence. I tried uninstalling and disabling this addon but alas, it came back to me like a boomerang. I finally was able to uninstall it using a special tool that I got from the Ask toolbar FAQs, which probably cleaned my registry of any
remnants of the Ask addon. Now, my Visual Studio debug sessions always function properly and debugging my web pages is a lot less frustrating.
Jun 27, 2013 09:53 AM|mvolo|LINK
The biggest cause of Visual Studio hanging during debugging is function evaluation, which is done anytime you hover over a variable or have variables added to your watch window. VS needs the thread to execute to a "safe point" in order to trigger the evaluation
of your variable. This can sometimes take a long time, esp. in Release mode when the code is optimized.
The best ways I've found to reduce hanging:
1. Turn off "Enable property evaluation and other implicit function calls" in Debugging\General options
2. Close the "Parallel stacks" window if you have it open
3. Remove items from your "Watch" window
4. Debugging processes with very high numbers of threads is slow because the debugger has to pause/resume all threads. Reducing number of threads during debugging really helps, which is why we dial down our threading use in debug mode.
Former ASP.NET PM
Founder/CTO at LeanSentry
Jun 27, 2013 12:35 PM|rmdw|LINK
Thanks for the tips, Mike. I've just effected #1. #2 isn't an option in my case. I only have a few items in the Watch window but do need them.
We'll see if this cures the problem.
Jul 02, 2013 12:28 PM|pkpjpm|LINK
This problem has affected me for about 6 months. It seems to happen consistently when I'm debugging a paritcular Azure MVC Cloud Service project. I've found that option #1, disabling property evaluation, is an effective workaround. However, you then obviously
loose property evaluation, which is a pain. I retested after applying update 2 and just yesterday after applying update 3 and I was very disappointed to see that the problem is still present.
I had previously submitted input on a connect issue related to this problem, but now I can't find it.