I have VS2010 Professional edition and I recently started getting problems debugging an MVC website. The debugging at the Controller code is very slow and each F10 command takes 20 seconds to move to the next line.
Javascript code debugging is quick. I tried a console app and a Forms app and debugging is quick. I also tried creating a blank new MVC app website and the debugger slows down. I am using IIS7.0. This recently started happening as I recently installed VS2012 Ultimate RC. I thought it may be the reason and uninstalled all the software VS2012RC Ultimate installed on that day and the debugger retuned to normal. Looking at task manager devenv.exe was using about 1GB of memory and w3wp.exe was also consuming memory and increasing to 800MB. Has anyone recently installed VS2012 RC Ultimate alongside VS2012 Professional and got into similar problems? Does any one who what is the rootcause of this problem?
Try setting IntelliTrace to collect events only in Options -> IntelliTrace -> General. This might speed up debugging.
Related
I have an intermittent issue when trying to debug local IIS sites.
Visual will hang and eventually displays the error:
The web server did not respond in a timely manner. This may be because another debugger is already attached to the web server
If I wait a minute and hit "Start Debugging" again it will work (sometimes I may get the error several times but it eventually works).
There is nothing in the Event Viewer around the times I try to debug.
The app pool is .net V4.0 Integrated.
I am running Windows 8 Pro with IIS 8 and Visual Studio 2010.
Also its a site using EpiServer 6 R2.
I have tried IISReset, stopping/starting the site, closing and reopening Visual, rebooting my machine. None of that seems to make a difference, its hit and miss whether the solution will debug or not.
Once the solution is debugging, it runs fine without issue. Until I stop debugging and try and start debugging again.
The site runs fine in all other aspects, its only when I try to debug.
So... I never fixed this issue, but have since upgraded to a solid state drive. So I now have a fresh install of Windows 8 Pro and Visual and the issue has not resurfaced.
When i debug apps on windows7 using VS 2005, it's very slow. just general slowness. works fine on xp.
running outside of the debugger is normal. Even when i start apps outside the debugger then attach and debug it is normal.
im running VS 2005 in Vista compatibility mode.
Any idea what i can do to prevent slowness when debugging?
Seems like the problem happens periodically and is related to the amount and location of breakpoints set in the debugger. The problem can be worked around by attaching to the process after starting it.
For a complete solution, probably need vs2008.
I'm a .Net developer running Windows 7 Ultimate (x64) on a 2010 MacPro (2.27Ghz/6GB RAM) using Bootcamp. Until about a month ago its been, imo, the ultimate dev workstation. However recently I've noticed that Visual Studio 2010 takes a very long time to redraw its windows. This is most noticeable when switching to it after its been in the foreground.
I don't get this problem with other Windows apps and am baffled because the machine has more than enough grunt to handle a few MDI'd windows yet grinds for up to five minutes sometimes when reactivating the VS environment - the screen update seems to slow everything down. My colleagues are using identical hardware and software but running Windows under Parallels on their Macs does not lead to this behaviour.
I'm getting desperate (and I've asked this same question at apple.stackexchange.com) - does anyone know why this might be happening and whether there's a fix ...?
Improving Performance by Changing the Visual Experience
You might have a problem with Hardware Acceleration in VS2010. I had an issue with rendering applications built using WPF because of this.
Give it a try:
http://blogs.msdn.com/b/zainnab/archive/2010/06/22/improving-performance-by-changing-the-visual-experience-vstipenv0017.aspx
And if that doesn't fix your issue, go to your video card settings (nvidia or amd) and do a "reset settings". Then try again.
Recently, my coworker and I upgraded our development environment to Win7 x64 with VS2010 Pro. Our application is specifically targeted at x64 platform.
The problem we are encountering is during debugging, when attempting to step through the code (F10), at least 50% of the time VS will simply lock up the application being debugged. The IDE has the appearance of having pressed F5, but the application is not responsive and we have to force stop the application.
Our application is a Client (GUI) and a Server that communicate through .NET remoting.
This is starting to directly affect our productivity, so if anyone has any ideas what may be causing this, please let me know.
There is an outside chance that it might be the debug symbols loading. Check the status bar I think it tells you when the symbols are loading.
This may be a moot point, but have you installed the VS 2010 service pack 1?
There are various bugfixes related to debuggers included.
http://support.microsoft.com/kb/983509
I had a similar problem. it turned out that a higher level program had a different run-time library (multi-threaded debug dll), while my app was simply a multi-threaded debug. Once I converted mine to a multi-threaded debug dll, the freeze stopped happening.
I am attempting to create a simple silverlight 4 application in visual studio 2010 ultimate running on windows 7 x64 and I am unable to use f5 debugging.
The error is:
Unable to start debugging. A fatal
error occurred. For more details,
please see the Microsoft Help and
Support web site. HRESULT=0x8004005.
In researching this I see a few people who say that reinstalling the developer runtime will correct the issue. I have done this several times but the issue remains. I have also tried running without debugging (works fine) and then attaching the debugger to the ie silverlight process, however this doesn't work either (it only breaks on the 'throw new Error(...)' javascript eval code.
I can do f5 debugging of asp.net projects without issue.
I have looked at several other silverlight debugging posts and either their error is different or their solution did not work for me.
This appears to have been caused by a windows phone 7 tools beta. By uninstalling it and installing the rtm version, the issue went away. shrug