-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Language server doesn't stop when quitting VSCode (Linux) #671
Comments
Is the editing still working for you at that point in time? |
@razzeee I don't understand the question, sorry. Maybe I wasn't clear. After quitting VS Code the elm language server still keeps a process running. I would expect that quitting VS code would kill the lsp process. Happy to provide more info and help. |
It would be interesting, if you could still use the lsp before that. If it was already stuck on something at that point, it might explain, why it misses the shutdown. |
I can confirm that this happens when the LSP stops responding. I don't know how it gets into this state, it appears that this happens when I change things too quickly, but unsure. I notice this when the LSP stops formatting my code on save. Then if I quit the node process keeps going and I need to kill it manually. So the cause of the issue that the LSP becomes unresponsive. |
Yeah, that's going to be harder to track down, but good, that we can narrow it down. |
I noted that after quitting VSCode the language server keeps running on the background.
Expected Behavior
Stop the server process
Current Behavior
I open VS code, the LS starts. Then I quit VS Code but the LS keeps running. Doesn't happen all the time, but often enough.
I have to kill the process manually.
Steps to Reproduce (for bugs)
Your Environment
Thanks
The text was updated successfully, but these errors were encountered: