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
{{ message }}
This repository has been archived by the owner on Nov 12, 2018. It is now read-only.
So I was doing atom ~/.zshrc to edit my shell config file and noticed the fans on my Macbook Pro going crazy after a while.
Looking at the activity monitor I find:
Inspecting that I could see that Atom was the parent process. After quitting Atom however the beam process remained, eating up all my CPU power as a zombie process until force killed. Disabling autocomplete-elixir avoids the process from spawning.
Another sad fact is that I don't even have a single Elixir project on my harddrive at the moment.
Would suggest:
Don't spawn the beam process at all unless there are any elixir files in the currently open project
Gracefully exit the beam process when closing elixir projects (and obviously when shutting down Atom completely)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So I was doing
atom ~/.zshrc
to edit my shell config file and noticed the fans on my Macbook Pro going crazy after a while.Looking at the activity monitor I find:
Inspecting that I could see that Atom was the parent process. After quitting Atom however the beam process remained, eating up all my CPU power as a zombie process until force killed. Disabling
autocomplete-elixir
avoids the process from spawning.Another sad fact is that I don't even have a single Elixir project on my harddrive at the moment.
Would suggest:
The text was updated successfully, but these errors were encountered: