-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
High CPU usage from ra_lsp_server process #2023
Comments
There were some fixes around chalk and panicking that your build does not have. Can you update to latest master and try again? |
Sounds like #1958. |
Yeah, this looks like a known bug in notify. It might have been fixed with the recent upgrade. A workaround is to switch to client-provided watching in the settings. |
I've got Oct31 build on OSX (5451bfb) and getting high cpu usage on laptop when I woke up. Must be notify as this was the only thread that was not waiting on something. My laptop lid was closed, it should have had a good nights sleep... will try client provided watching. Interestingly the workload doesn't go down even if I shut down vscode. Here was my notify thread's bt:
|
@gilescope i had the same situation, laptop lid was closed, also closing VScode didn't kill it |
I haven't been writing any Rust today, but noticed my fans spinning.
I saw
ra_lsp_server
is running at around 90% CPU usage.I ran
lldb
on the process(it says process stopped but it's still running)
I ran
bt
bt all
Commit ID: 58dc3b1
The text was updated successfully, but these errors were encountered: