After some usage I see several LSP instances running

[megatux]

$ ps ax|grep ruby-lsp
44141 ?? S 0:07.40 /Users/megatux/.asdf/installs/ruby/2.7.6/bin/ruby-lsp
46489 ?? S 0:06.44 /Users/megatux/.asdf/installs/ruby/2.7.6/bin/ruby-lsp
46610 ?? S 0:06.34 /Users/megatux/.asdf/installs/ruby/2.7.6/bin/ruby-lsp
46684 ?? S 0:06.33 /Users/megatux/.asdf/installs/ruby/2.7.6/bin/ruby-lsp

[vinistock]

Can you provide more details? What are the steps you need to take to end up in this scenario? Are you on the latest version of the ruby-lsp gem?

[megatux]

Version ruby-lsp (0.3.7).
I think the easiest steps to reproduce it are,

• having the Gemfile with the ruby-lsp gem added but not commited
• from terminal: git staging
• moving back to vscode (it will prompt to install the ruby-lsp gem)

- do not install it - going to terminal again and `git stash pop` so the Gemfile is restored w/ruby-lsp gem - going back to vscode and clicking on [Run bundle install]

this creates a new ruby-lsp process here.

Env: Macbook M1, Ventura. brew + asdf for version manager.

[vinistock]

Thank you for the reproduction steps. We watch the Gemfile to trigger client restarts, so maybe the issue is that we aren't awaiting the start here.

[vinistock]

If you have a chance, can you please try the latest v0.0.13 release and check it the issue is fixed?

[megatux]

Great! thanks, updated the extension to that version. Will report any issue I found. Regards