Vscode-remote-release: WSL2: server process not terminated on exit

Created on 16 Jun 2019 · 5Comments · Source: microsoft/vscode-remote-release

Version: 1.36.0-insider (user setup)
Commit: 15b7c86d86319b187a5ef255c170184a8519c5af
Date: 2019-06-14T10:37:04.235Z
Electron: 4.2.4
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18917

In WSL2, the VS Code Server process is not terminated when the VS Code instance is closed, and it is not reused when a new window is opened (after all previous ones are closed):

After I started two instances of VS Code and close them both, I can still see all of the processes associated with both instances, and the resource consumption is noticeable (both CPU and memory), until I manually kill the processes:

Notice the resource consumption with all VS Code windows closed:

wsl

Source

radu-matei

Most helpful comment

Yes seeing the same, system will be cluttered with left over node processes.
I'm getting in the habit of running pkill node but really this needs to be fixed

This is without a single instance of VS Code running!

benc-uk on 18 Jun 2019

👍2

All 5 comments

The same issue also occurs with the SSH version.

AlexanderLieret on 17 Jun 2019

👍1

Yes seeing the same, system will be cluttered with left over node processes.
I'm getting in the habit of running pkill node but really this needs to be fixed

This is without a single instance of VS Code running!

benc-uk on 18 Jun 2019

👍2

https://github.com/microsoft/vscode-remote-release/issues/203 will help here