Last post Mar 03, 2017 02:56 AM by paty20
Mar 04, 2014 12:49 PM|roschler|LINK
Recently, Visual Studio 2013 started hanging again when trying to debug/trace an ASP.NET web site. The site was created with WebMatrix 3 but I don't think that is relevant.
When VS2013 opens the web site Solution it takes a really long time to load up. Once it does load up and I run the project, it hits my first breakpoint and then the IDE Window quickly shows "(not responding)" in the title bar and the IDE is now hung.
This happened to me a long time ago and the root cause was needing to set the "use 64-bit IIS" option as indicated by this SO post:
Visual Studio 2013 crashes and restarts every time I run my test solution
But I triple-checked and I do have the 64-bit option checked. What can I do to fix this?
Note, I can run the project if I don't debug using Ctrl-F5. The hang happens when a breakpoint is set. It seems like whatever communication VS2013 has to have with IIS Express when it sets breakpoint isn't happening properly, and VS2013 is waiting without
time-out for an answer. But that's just speculation.
Mar 05, 2014 03:30 AM|Starain chen - MSFT|LINK
Do you have that issue with the new project?
First, please check whether there are the enough resource (E.g. Memory) to use.
Secondly, please check whether there are any errors in the Event Viewer.
On the other hand, please try to repair or re-install the VS2013.
Mar 05, 2014 12:23 PM|roschler|LINK
I have 4GB of free memory when this happens.
There are no errors in the event viewer related to VS2013 or IIS Express.
I just did a Repair of VS2013 and then completely uninstalled and re-installed IIS Express.
The problem still happens. Note, when I first start VS2013 but only with ASP.NET projects (web projects and any web project), the editor is very sluggish. Every time I click on a different line of source in a web page there's
a noticeable 1 second pause. The same applies to Menu items. After about 5 minutes that condition goes away.
But as soon as I click F9 the IDE freezes (not responding). After about a minute or two the IDE comes back alive. But if I click anywhere inside the IDE it freezes again and the process repeats making it essentially unusable. I ran the SysInternals ProcMon
utility and it shows the IDE making a TCP send to IIS that is never answered. There appears to be something wrong with the two programs talking to each other, but that wouldn't explain the sluggishness mentioned above.
What is really strange is that this was the exact problem I experienced months ago that didn't clear up until I activated the setting that tells VS2013 to use the 64-bit version of IIS. After that for a while I had no problems debugging ASP.NET projects
in VS2013 and I did not have the sluggish response in the IDE mentioned above. Apparently something changed in the last month or so to bring the problem back, but with a different cause.
- Turning off Windows Defender/Firewall did not help
- This happens only with ASP.NET projects, not Windows Phone, Desktop, or WinRT
PURE SPECULATION: It feels like there is some code in the IDE that is running absurdly slower than usual. It almost feels like what happens when you have time consuming debug statements in code that you forget to turn off that brings your app to a crawl
when you run it. But in this case, the problem is with the VS2013 IDE. I say this because that would explain the sluggishness in the IDE and the IDE going away for a few minutes and coming back until you activate the IDE window again, only for that vicious
circle to repeat ad infinitum. I thought it might be a full time-out on the TCP connection after the IDE does a send, but the typical time-out value for sockets is usually 30 seconds to a minute. If the TCP bridge code was hampered in a way like this, then
it might be the reason for the problem. Only Microsoft can answer that speculation of couse.
Mar 06, 2014 12:46 AM|Starain chen - MSFT|LINK
Please check whether it is enabled Edit And Continue for the ASP.NET project. If it is enabled, please try to disabled and check the result.
There is a link may benefit you:
# New IIS Express Behavior in VS 2013
Mar 06, 2014 12:55 AM|roschler|LINK
Thanks Starain, but I turned that off a few days ago and it did not help. I just checked, it's still off and I still have the problem.
Mar 09, 2014 11:21 PM|Starain chen - MSFT|LINK
You could submit this feedback to Microsoft Connect feedback portal:
http://connect.microsoft.com , Microsoft engineers will evaluate them seriously. Thanks for your understanding. After you submit the feedback, you can post the link here which will be beneficial for other members with the similar issue.
May 23, 2014 10:08 AM|KakCAT|LINK
I'm suffering the same problem. Did you fix it?
Oct 28, 2014 03:15 PM|somecoderASP|LINK
this may sound like a silly solution, but you might try launching Visual Studio using Run As Administrator. I found that fixed my problems with both VS2008 and VS2013 hanging on breakpoints in native apps when running visual studio under Windows 8-64.
Mar 03, 2017 02:56 AM|paty20|LINK
trank excelent resp