Skip to content
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

Open
sporto opened this issue Jul 27, 2021 · 5 comments
Open

Language server doesn't stop when quitting VSCode (Linux) #671

sporto opened this issue Jul 27, 2021 · 5 comments

Comments

@sporto
Copy link

sporto commented Jul 27, 2021

I noted that after quitting VSCode the language server keeps running on the background.

Expected Behavior

Stop the server process

Current Behavior

image

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)

  • Using Ubuntu 21.04
  • Open VS code, edit Elm code for a while
  • Quit VS code

Your Environment

  • Version used: 2.2.0
  • Editor name and version (e.g. VSCode 1.36.1): VSCode 1.58.2
  • Environment name and version (e.g. node.js 5.4): node 14.15.1
  • Operating System and version: PopOS 21.04 (based on Ubuntu 21.04)

Thanks

@razzeee
Copy link
Member

razzeee commented Sep 17, 2021

Is the editing still working for you at that point in time?

@sporto
Copy link
Author

sporto commented Sep 18, 2021

@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.

@razzeee
Copy link
Member

razzeee commented Sep 18, 2021

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.

@sporto
Copy link
Author

sporto commented Oct 6, 2021

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.

@razzeee
Copy link
Member

razzeee commented Oct 6, 2021

Yeah, that's going to be harder to track down, but good, that we can narrow it down.

@razzeee razzeee transferred this issue from elm-tooling/elm-language-client-vscode Dec 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants