VS 2017 - very slow (lagging) when debugging

Question

When I debug my solution, vs 2017 is very lagging and slows it down, as if it should work with something heavy in the background.

Thus, he stops responding every 5 seconds for 2 seconds, which is very annoying. Any suggestions?

EDIT (tried suggestions):

• The link to the browser is disabled.
• Stopped customer feedback

Answer 1

After some additional research, I found this thread. Uncheck the Enable diagnostic tools during debugging box in Tools → Options → Debugging → General trick!

Uncheck Enable JavaScript for ASP.NET in JavaScript debugging
Tools → Options → Debugging → General
makes a huge difference in performance.

Answer 2

If you disable the diagnostic tools, do not fix the problem, try disabling IntelliTrace. Uncheck the Enable IntelliTrace box in Tools → Options → IntelliTrace. Work for me.

Answer 3

I tried to disable several things myself, to see what causes it. The only thing that worked for me was Tools> Options> Debugging> General> "Enable JavaScript Debugging for ASP.NET (Chrome and IE)."

I am using VS2017 Enterprise v15.2 for Asp.net WebForms.

Answer 4

I also experience a delay when checking "Enable Javascript Debugging for ASP.NET (Chrome and IE)." And disabling "Enable diagnostic tools during debugging" did not help.

However, I also noticed that when I F12 for Chrome Developer Tools, the latency lags and the application runs.

Hope this helps.

Answer 5

Hiding the Threads window did the trick for me.

Answer 6

Only one thing that helped me was to disable the Debugger parameter for Resharper. If you use Resharper , try UNCHECK "Show local variable values ​​in the editor" in the menu: Resharper → Options → Tools → Debugger .

It helped me.

Answer 7

I had the same problem. In debug mode, my webforms project was very slow. When using Ctrl + F5, it starts quickly (as during deployment). I found a try / catch block that ran 45 times. He did nothing, it’s just a trap for the mistake I made. I fixed the error and removing the try-catch block - voila! - return at full speed.

So, if you ran into this problem and you tried all of the above solutions (I did), find the catch try block, which often works. [Correct your mistake :)], and then delete the try-catch block. I cannot believe the difference he made. Of course, there was no difference, since the try-catch block did nothing, but it did.

Answer 8

I refused to get Debugging => Bind to the process , working ... even tried ALL the solutions in this SO post (2 pages).

Decision

Use the ReAttach VS IDE Extension . This circumvents the need to ever use the Attach to process dialog if it is a process that you recently connected to.

Answer 9

If you are using VS 2017 Enterprise, try disabling the IntelliTrace function (Tools → Options → IntelliTrace)

when this function is disabled, the delayed behavior disappears even by turning on the diagnostic tools (Tools → Options → Debugging → Enable Diagnostic Tools during debugging)

Answer 10

Sometimes this happens due to real-time scanning in Anti-Virus.

" Add Exceptions " Visual Studio Files / Folders for Your Antivirus

C: \ Program Files (x86) \ Microsoft Visual Studio \ 2017 \ Professional \ Common7 \ IDE \ devenv.exe

C: \ Program Files (x86) \ Microsoft Visual Studio \ 201

Answer 11

What worked for me was to delete all of the following folders in the solutions directory:

• .vs
• x64
• Debug
• Release

Answer 12

I had this problem when the program worked more slowly, if it was launched from Visual Studio, there were too many threads, for example, a lot of new System.Threading.Thread () in a loop, etc. I switched the code to use ThreadPool instead with Task, etc. and the slowness is gone.

Answer 13

The workaround I used was to run msvcmon.exe locally with administrator mode before running the debugger. Then launch the connection window and provide the remote port for debugging.