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

ElixirLS Running two instances on Vscode #321

Closed
tuomohopia opened this issue Jul 16, 2020 · 0 comments
Closed

ElixirLS Running two instances on Vscode #321

tuomohopia opened this issue Jul 16, 2020 · 0 comments

Comments

@tuomohopia
Copy link

tuomohopia commented Jul 16, 2020

Problem

ElixirLS runs two instances on my Vscode. They both do exactly the same work at their own pace, maxing out my CPU usage all the time. I can see two beam.smp instances in my Mac's Activity Monitor Panel, and likewise two ElixirLS instances in Vscode's Output panel where extensions display their logs.

Even when seemingly doing nothing (logs don't show any new entries), they both keep maxing out my CPU.

The logs on both start with:

Started ElixirLS v0.5.0
Elixir version: "1.10.3 (compiled with Erlang/OTP 22)"
Erlang version: "22"
ElixirLS compiled with Elixir 1.7.4 and erlang 20

The logs appear constantly identical, except the times to compile files are slightly different, indicating they are indeed two different instances doing the same things at the same time.

mix.exs dependencies also have {:dialyzex, "~> 1.2.1", only: [:test, :dev]},, in case that is anyhow relevant.

I'm using asdf with the following content in my .tool-versions:

elixir 1.10.3-otp-22
erlang 22.3.4.1
nodejs 11.15.0

Environment

  • Elixir & Erlang versions (elixir --version):
    Erlang/OTP 22 [erts-10.7.2.1] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe]
    Elixir 1.10.3 (compiled with Erlang/OTP 22)
  • Operating system: macOS Catalina 10.15.6 (just installed a major update)
  • Editor: VSCODE
  • LSP Client name: ElixirLS: Elixir support and debugger

Edit:
Sorry this bug report may have been to the wrong repo!
Here's the issue I opened at vscode-elixir-ls:
elixir-lsp/vscode-elixir-ls#125

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

1 participant