Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

VS2010 Debug entry very slow

When I start debugging my web application either from Start with Debugging (F5) or attaching to the ASP.NET worker process it will load the assemblies from the application very slowly that I can individually read the names of them as they scroll through the status bar of VS2010.

When I start debugging I see that MSVSMON.exe uses 50% CPU and locks at 50% clearly filling up a full core. Also seeing that this is described as Visual Studio Remote Debugging Monitor, I'm confused if this should even be used since I'm debugging everything local to my machine.

I am running my environment virtually connected by RDP if that could be related to this.

Host Machine: Server 2008 Enterprise R2 Dualcore Xeon 2.53ghz

Virtual Instance: Win7 Enterprise 6gb ram full processor allocation

Does this seem normal? Should MSVSMON even be running if I'm debugging locally?

like image 875
Chris Marisic Avatar asked Jul 14 '10 18:07

Chris Marisic


People also ask

Why is debug mode slower than release?

In Debug mode, there are no optimizations, which means debug builds can run slower than Release build.

Is debug slower than run?

Unfortunately, debugger speed has some runtime limitations, which can't be easily fixed. If your code does some high performance computations, Debugger will be at least 3 times slower than usual Run.

Why Visual Studio is very slow?

You might have extensions installed that slow Visual Studio down. For help on managing extensions to improve performance, see Change extension settings to improve performance. Similarly, you might have tool windows that slow Visual Studio down.

How do I skip the code while debugging in Visual Studio?

You can also click on the line you want to skip to and hit Ctrl+F10 (Run to Cursor). It will jump directly to that line.


2 Answers

Menu.Debug.DeleteAllBreakpoints

Worked for me.

like image 161
Jay Borseth Avatar answered Nov 08 '22 11:11

Jay Borseth


Yes, msvsmon.exe will be used when you debug a 64-bit program. Since Visual Studio is completely 32-bit, the remote debugger is needed to bridge the divide.

There isn't any reason to assume that the slowdown is caused by it being a remote debugger. Working mightily to find and load the .pdb files would be likely. Or accidentally having the mixed-mode debugging option turned on so the debugger is also seeing all unmanaged DLL loads and finding symbols for them. These are just guesses of course.

like image 43
Hans Passant Avatar answered Nov 08 '22 12:11

Hans Passant