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.
Closing VS Code notebook orphans dotnet processes on MacOS
See original GitHub issueVS Code extension on Mac version v1.0.2462010
#!about Version: 1.0.246201+da749355d416da20e634e5c80073b92356b57e0e
MacOS using VS Code Version: 1.60.2 macOS Big Sur 11.6
Open/create a dib notebook. After running a C# cell, close VS Code with Cmd-Q.
There are two dotnet processes each consuming a whole core.
I have to kill these processes manually because they aren’t killed when VS Code exits.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:18
- Comments:33 (12 by maintainers)
Top Results From Across the Web
User and Workspace Settings
To modify user settings, you'll use the Settings editor to review and change VS Code settings. To open the Settings editor, navigate to...
Read more >dotnet processes left behind on macos
Hi, When running dotnet projects from the cli, vs for mac, or vscode, i seem to end up with lots of dotnet processes...
Read more >Can't kill frozen Visual Studio code on mac - Ask Different
1 Answer 1 · kill all node processes · Delete the VSCode and all related files · Using an app like app cleaner...
Read more >Visual Studio Code - Terminal Blank Screen
My solution for VSCode 1.39.2 with Ubuntu has been: File -> Preferences -> Setting -> Features -> Terminal -> Inherit Env.
Read more >Navigating your code in VS Code - YouTube
This Code 0 to 20 provides an in-depth look at quickly and efficiently navigating through your codebase. The video covers a range of ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m experiencing the same issue. The bug makes it impossible to use the tool via Azure Data Studio. Had to drop the extension.
Same here. dotnet is going haywirewire on M1 running under dotnet interactive and vscode. Had to manually close them otherwise I have like several 100% CPU dotnet processes running at the same time.