VS debugger running slowly? Check your breakpoints!


If you’re finding that the VS debugging seems to get slower and slower (especially when you first crank up a process), one thing to look for is unresolved breakpoints. That is, breakpoints that the debugger can’t set just yet, as the module/assembly hasn’t loaded yet.


In my particular scenario, I had several dozen breakpoints from an old debugging session with a particular DLL. I had since switched my attention to a completely different process, but the debugger was still valiantly examining each DLL as it loaded to see if it should set any breakpoints in it. When a process load dozens of DLLs, and you have dozens of breakpoints to check for each DLL, it’s no wonder things aren’t as speedy as you might once remember.


The moral of the story: Go to the breakpoint window every once in awhile to clean out old unneeded breakpoints.


 


Comments (4)

  1. Daniel says:

    Hey Matt!

    We love your posts, how about updating more often? 🙂

  2. Al Glushchenko says:

    ..or at least have those extra BPs disabled. I love putting dozens of them, too – especially when going thru your code and the code of Barry T. – you Matt must remember that W..l core :), and unless I disable most of BPs that I don’t need right now, my VS gets tremendously slow.

    Not taking about conditional breakpoints…

  3. Jagan Raja says:

    Thanks alot,That worked for me,

    Additionally below some steps pated for debugging fast.

    Web Application

    – Open a browser and type in your url (http://localhost/WebApplication1)

    – Navigate to that page which you want to debug

    – Now open your solution if it is not opened already

    – Now Go to Menu Debug >> Processes

    – Now select the Process(aspnet_wp.exe) from the Available process list

    – And click on Attach

    – Now you are ready to debug.

    Windows Application

    – Click on your Application (.exe)

    – Go to that form which you want to debug

    – Now open your solution if it is not opened already

    – Now Go to Menu Debug >> Processes

    – Now select the Process from the Available process list

    – And click on Attach

    – Now you are ready to debug.

    I hope above mentioned steps are usefull to others too.

Skip to main content