You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've recently installed the plugin and noticed our VM was running at near max capacity. This could be us not terminating vscode correctly but just FYI, we killed these processes manually. We have two seperate vscode instances connected but have a few tabs open. Seems reconnecting the next day doesn't kill it?
I am seeing the same behavior in my local environment, which is VS Code on WSL. I can open a new VS Code window, start up the language server, then close the window, and in WSL I can see the language server JAR still running. So I guess the extension doesn't automatically kill any child processes when the window is closed.
I can run "Stop language server" from the command palette and I see the language server is killed.
I will try stopping the language server automatically when the extension is deactivated, in the next patch release. I'm not sure how it will work with your particular setup since VS Code can run in a lot of different environments, but we'll give it a try
Hello,
We've recently installed the plugin and noticed our VM was running at near max capacity. This could be us not terminating vscode correctly but just FYI, we killed these processes manually. We have two seperate vscode instances connected but have a few tabs open. Seems reconnecting the next day doesn't kill it?
The text was updated successfully, but these errors were encountered: