VS 2005 debugger running like molasses

  • Thread starter Thread starter Clive Dixon
  • Start date Start date
C

Clive Dixon

Recently the solution my team is working on has sometimes been running like
mloasses under the debugger. Pressing F10 to go to the next statement, even
if that step apparently does nothing (e.g. going from the opening brace of a
method or property accessor to the first actual code statement) can
sometimes take 20-30 seconds. Now the only thing I can think of is that
recently I have been making liberal usage of DebuggerDisplay,
DebuggerTypeProxy and writing some debugger visualizers. But surely these
should only be used at the point where the data is examined and shouldn't be
affecting the speed in the way we are experiencing. Anybody any ideas what
might be causing this behaviour?
 
Hello,
Recently the solution my team is working on has sometimes been running
like mloasses under the debugger. Pressing F10 to go to the next
statement, even if that step apparently does nothing [...] can sometimes
take 20-30 seconds.
Click to expand...

Doesn't sound your Visual Studio isn't working the way it should. But before
giving ideas of what might be wrong, we'd need more information. For
instance:

- Do all of your Visual Studio solutions have the same problem?
- If you ask your colleague to debug the problematic solution, does s/he
experience the slowness?
- Which operating system and Visual Studio version are you using?

Thanks!

--
Regards,

Mr. Jani Järvinen
C# MVP
Vantaa, Finland
(e-mail address removed)
http://www.saunalahti.fi/janij/
 
VS2005. Some of use are using XP SP2, some using Vista. We are all
experiencing this slow debugging performance problem. We only have one
solution we are working with.

We have been trying to modify various VS settings (e.g. enabling or
disabling "Edit & continue", checking or unchecking "Just my code"), but all
to no avail.

Jani Järvinen said:
Hello,
Recently the solution my team is working on has sometimes been running
like mloasses under the debugger. Pressing F10 to go to the next
statement, even if that step apparently does nothing [...] can sometimes
take 20-30 seconds.
Click to expand...

Doesn't sound your Visual Studio isn't working the way it should. But
before giving ideas of what might be wrong, we'd need more information.
For instance:

- Do all of your Visual Studio solutions have the same problem?
- If you ask your colleague to debug the problematic solution, does s/he
experience the slowness?
- Which operating system and Visual Studio version are you using?

Thanks!

--
Regards,

Mr. Jani Järvinen
C# MVP
Vantaa, Finland
(e-mail address removed)
http://www.saunalahti.fi/janij/
Click to expand...
 
Back
Top