Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Debugger is laggy in VS Code 1.30

See original GitHub issue

Environment data

dotnet --info output: Version: 2.1.401 Commit: 91b1c13032

Runtime Environment: OS Name: Mac OS X OS Version: 10.14 OS Platform: Darwin RID: osx-x64 Base Path: /usr/local/share/dotnet/sdk/2.1.401/

VS Code version: 1.30.0 C# Extension version: 1.17.1 & 1.18.0 beta-2

Steps to reproduce

Running dotnet core application in debugger (using F5).

Expected behavior

Running as fast as it can run.

Actual behavior

It’s lagging my VS Code, sometimes giving me message that vs code is not responding, quite heavy cpu usage for extended period of time. Overall debugger is not working properly.

Additional info

This wasn’t issue when using VS Code 1.29 maybe upgrading VS Code is causing this.

Issue Analytics

State:
Created 5 years ago
Comments:11 (1 by maintainers)

Top GitHub Comments

1reaction

visiblesoft-escommented, Jan 24, 2019

Hi, same problem here (vscode 1.30.2, omnisharp 1.17.1). Working with mac osx.

When I launch app debug all works fine, queries to SQL db are fast, but after some seconds every time my frontend request data, vscode stop responding during several seconds (+/- 40sec). If I stop debugging and launch again all works fine again during some time.

No errors appear in console, only vscode appears to stop working for several seconds, receiving sometimes the dialog asking to Keep Open or Close vscode.

Tested the same application debugged with Visual Studio for mac and it works fine without problems. Regards Jose

1reaction

TomStarycommented, Dec 20, 2018

I just tried new version of insiders version of VS Code and in this version everything works normal like in 1.29 version of VS Code.