-
Notifications
You must be signed in to change notification settings - Fork 70
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
install_cli.py script and possibly other scripts running in background causing high cpu usage #192
Comments
For now, add this line to your neovim config: What's the contents of your |
Thank you @alanhamlett for the and sorry for the late reply on my part. Are you sure it's
As for the
Also, I tried to manually run the never-ending command, which is:
and it works fine: runs and says the CLI is up-to-date, not sure why it gets stuck (or seems to be stuck) when I open Neovim |
Oops, sorry I thought it was a global variable that we could have used to disable auto-updates but it's a script local variable that only exists inside the plugin scope. The two ways to disable auto updates are putting
That means the Python script is working, and the problem seems to be in how the plugin is executing the Python script: vim-wakatime/plugin/wakatime.vim Line 169 in cf51327
By chance, do you have |
Hi, I noticed that my CPU usage has gone very hight.
After some digging, I realized that every time I start neovim, a new process calling
is started on my Mac and keeps running forever.
Also I see another script running having this command:
which is also probably coming from Wakatime since it starts when I start Neovim.
Since the scripts are running forever, eating my CPU, I stopped them, but then I see an error/message in Neovim showing
[Wakatime] 143:
Is it possible to investigate what's going on causing this issue?
Thank you
The text was updated successfully, but these errors were encountered: