microsoft / microsoft/vscode-dotnettools
A large number of .NET host instances were not destroyed.
Open
Nobody has claimed this yet.
area-sdk
bug
msbuild
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Describe the Issue
vscode version 1.102.1
There are many instances in .net host that cannot be destroyed after VSCode is closed
There is a very interesting phenomenon: if I keep the Task Manager open, these .Net Host processes are all in a process group named dotnet.exe (after some time, this process group is renamed to .NET Host) as child processes. When I close the Task Manager, all the .Net Host processes disperse into individual processes.
Steps To Reproduce
No response
Expected Behavior
No response
Environment Information
win11
vscode version 1.102.1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.