-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
helpServer never exits on reload window #911
Comments
On my machine (windows 10) this bug is actually caused by #912, which is why I used |
Looks like |
Does |
Maybe related: pkrumins/node-tree-kill#27, pkrumins/node-tree-kill#28. |
I tried using |
Would you like to confirm if |
@ManuelHentschel @ElianHugh Do you have access to Windows and check whether it works as expected? Maybe we'll need another quick release, as the leaking help server processes are more and more on Linux and macOS machines on each extension activation. |
I won't have access until the weekend unfortunately. |
On Linux and macOS, the help server could be properly killed in debug mode, but not in normal use. Still looking into this. |
The help server processes are following:
The process we keep track is the shell process where
|
I wonder if the pid or cp object is somehow lost during the reload process? |
Looks like it has something to do with
I tried switching to |
Like #902, the help server process never exits when I reload vscode window. More specifically, whenever the extension is activated, a new help server process is started. But when the extension is deactivated or even when vscode exits, the help server processes never exit. As a result, the server will have more and more help server processes.
I have to manually kill all help server processes via
The text was updated successfully, but these errors were encountered: