Make Debugging faster
It takes too long to begin debugging an application. It also takes too much time stepping through code in debug mode.
@mjohn -- you're probably right as I've only worked with native C++ in VS-2012. But I do give them credit for making improvements with 'native', as this was much slower prior to Update 1 of VS-2012.
After microsoft use .net framework, every software is very slow in my computer. sqlserver manage studio is slow, microsoft dynamic crm is very slow to startup, visual studio is very very slow. my copmuter often shoutdown by itself because the cpu's temperature is too height.
@Dave Novak, you use native C++, not manage code, native is more faster.
It's April 2013 and it seems like debugging a native Windows Phone 8 app on a HTC 8S is really slow. Takes like 3 seconds to step in one line. The emulator is lightning fast compared to this but I also have some issues with deployment on an ARM device compared to X86 so I can't use that for proper debugging anymore :|.
For me, debugging native C++, recent product updates to VS-2012 have significantly improved performance. Removing my votes for this now.
I've reactivated the Connect issue:
MS has admitted that Mixed Mode debugging can be VERY slow. It will require some re-architecting to fix. Please upvote this Connect issue even though it's marked Deferred -- I can't find a way to re-open it.
I am using VS2010 (V10.0.40219.1 Sp1 Rel).
I am having issue:
debugging is too slow (30+ seconds to step through onne line ) when "enable property evaluation and other implicit function calls"..
please help me
I have the same problem, but switched to Forefox debugging everything works fast!
I wonder what they use in MS ...
VS Debugger commented
Hi Philippe, sorry to hear you're experiencing such a slowdown (and we appreciate the other feedback as well). Can you send me a mail so I can get more detail on your project? mariabl at microsoft. Looking forward to hearing from you.
I just noticed that under Visual Studio 2012 Release Candidate, debugging native code in a mixed-mode DLL is really slow. I have a class without ref modifier and as soon as I step into that function, debugging is order of magnitude slower and as soon as I am again in managed code, the debugger is fast again.
There is a factor of more that 10x slowdown. It happen weitheir on the main executable properties (C# application) I enable the native debugger or not.
Normally a few updates are done per seconds. When debugging that particular code, it take almost 5 seconds for each step. I have tried to close Intellitrace Windows and it does not help much. I have no breakpoint and only common debugging Windows opened (thread, stack, auto, local, watches).
There are no valid reason that the debugger would be much slower when debugging native code in a mixed-mode application that it is with managed code.
Avoid slowing down C++ code too much while debugging (when using STL containers). Also improving Edit and continue to works in more cases (C++/CLI, C# lamba...) and permit edition even if Edit and continue cannot compile them would make debugging experience faster.
And effectively, improving start time or stepping speed won't hurt even though in my case, it is generally not much a problem.
Steve, I sent you an email to (scarroll, not scarrolll). If you didn't get it, please contact me at dave.novak at xaviant dot com. Thanks.
Dave, can you send me a mail so I can grab more detail? scarrolll at microsoft. thanks.
I'm seeing this somewhat in both, though I think it's worse under VS-11, which is where I've been doing all of my debugging as of late. First breakpoint generally takes close to 30 seconds to respond after it hits and, from there, about 5-10 seconds to F10 between lines. Sometimes though it's much worse. It's very reproducible.
I never had these problems using Visual Studio 2008.
Dave, can you let us know if you are seeing this in Vs2010 or Dev11? we'd love to get a repro as that behavior is not typical or expected.
I don't know what's going on here, but stepping through C++ code in the debugger is HORRIBLY SLOW, especially after the breakpoint first hits. I've seen it take anywhere from a few seconds to close to a minute to F10 step to the next line. And I have a 64-bit Windows 7 machine with 16GB memory, an SSD, and an i7 3.8 GHz processor.
The debugger is PIG DOG SLOW and needs to be fixed!
Interesting, I just noticed that single-stepping though a C# program here at home (VS2010E) is quite fast, but at work it's much slower, at often one second per single step (but I'm on VS2008--we CAN'T upgrade because MSFT dropped WinCE support, although I am talking about the speed of local desktop debugging, not device debugging).
I think the main reason that debugging was slow in VS2008 is that when I single-step, all the editor tabs changed to show a "lock" icon--I can see each tab redrawing itself one-by-one--and then the "lock" icon disappears again--from each tab one-by-one. Is this fixed now, or is it just that my home project is configured differently?
Rich Howard commented
At some point, after edit and continue is done one or more times, debugger stepping goes from fast to unusable. Each step over or step into goes from fraction of a second to multiple seconds. This occurs for me after one or more edit and continues are done.
On a possible related problem, every edit and continue results in a recompile that is about twice the recompile time of the last edit and continue. Debugging becomes unusable after about 4 edit and continues. A restart of the app begins the process over. I never saw this slowdown in VS2008. I am a Winforms C# database developer.
David Cole commented
@Steve Carroll [msft]:
"David Cole, is the performance degradation you are seeing in template functions apparent when trying to step through them?"
Yes, both stepping *into* a template function and stepping *through* that function is slow, much slower than I would like it to be (several seconds per step is usual, and this is too slow) and significantly slower than stepping into or through non-template functions. Stepping into a template function generally feels slower than stepping through it for some reason.
"Dave, your issue sounds like it could be timeouts when trying to evaluate expressions in your call stack. One way to test this would be disabling the setting tools->options->debugging->Enable property evaluation and other implicit function calls."
I thought so as well and have played with that option already. Unfortunately, it has no visible effect.
I will contact you via email.
Hi. My name is Steve Carroll and I'm a development manager at Microsoft. My team is deeply interested in the feedback being provided here and would love to be able to get enough detail to reproduce these issues or collect profiling data of the debugger in these bad states. David Cole, is the performance degradation you are seeing in template functions apparent when trying to step through them? Dave, your issue sounds like it could be timeouts when trying to evaluate expressions in your call stack. One way to test this would be disabling the setting tools->options->debugging->Enable property evaluation and other implicit function calls.
You can contact me at firstname.lastname@example.org.