VS2010 Debugging recording is very slow

Question

When I start debugging my web application either from “Start with debugging” (F5) or join the ASP.NET workflow, it will load the assemblies from the application very slowly so that I can individually read their names when scrolling through the VS2010 status bar.

When I run debugging, I see that MSVSMON.exe uses a 50% processor and 50% locks, clearly filling the full core. Also, seeing that it is described as a Visual Studio Remote Debugging Monitor, I am confused if it even needs to be used, as I am debugging everything local on my machine.

I am launching my environment, actually related to RDP, if this could be related to this.

Host Machine: Server 2008 Enterprise R2 Dualcore Xeon 2.53ghz

Virtual Instance: Win7 Enterprise 6gb Full Processor Access

This is normal? Should MSVSMON work if I debug locally?

Answer 1

Menu.Debug.DeleteAllBreakpoints

Worked for me.

Answer 2

Yes, msvsmon.exe will be used when debugging a 64-bit program. Because Visual Studio is fully 32-bit, a remote debugger is needed to bridge the gap.

There is no reason to suppose that the slowdown is caused by the fact that it is a remote debugger. Most likely, the work of finding and downloading .pdb files. Or accidentally, the mixed mode debugging option is turned on, so the debugger also sees all unmanaged DLL downloads and finding characters for them. This, of course, is a guess.

Answer 3

Searching for characters is often very slow at the beginning of debugging, especially if you have one of the options for deleted characters, and do not set "ignore" in various DLLs that will not have characters on MS servers.

It can be not only things like third-party components of your code, but it can also intercept DLL files, for example, with graphic drivers, so you should watch what you are trying to load.

Running Fiddler ( http://www.fiddler2.com/fiddler2/ ) when you start debugging will show you whether characters will be deleted remotely.

Even if VS is not installed explicitly (in tools-> options-debug) for remote character selection, it will still follow the _NT_SYMBOL_PATH environment variable - check if this set is installed and what it points to.

Answer 4

I had the same problem, although this solution did not do this for me. In the end, I had to go to Tools-> Options-> Debugging-> Symbols and uncheck the location of the Symbol file (.pdb), and also click on the Empty symbol button. After that, debugging was much nicer.

Answer 5

For me, the problem was that I had a PUP (potentially unwanted program) that slowed down other processes. After a couple of times when MSVSMON showed this behavior, I found out that the Cltmng.exe process (from Search Protect by conduit) also took an unusual amount of CPU, removing it, solving the problem.