-
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
ra_lsp_server keeps hogging one core #2812
Comments
Can you get a backtrace for all threads? |
How would I get it to do that? |
$ gdb -p <pid of ra_lsp_server>
(gdb) thread apply all bt
(gdb) quit Or $ lldb -p <pid of ra_lsp_server>
(lldb) bt all
(lldb) quit |
I've been having the same problem as well. Heres my backtrace
|
From the above, this is the only thread doing any work:
|
I'm also seeing this, here's my backtrace on version |
I have also similar problems:
|
Adding my backtrace to the pile. I am using lsp-mode with emacs.
|
@shepmaster do you have seen similar behavior as me in #2879 ? |
Yes: emacs locks up for multiple seconds and I generally need to kill the rust-analyzer process and disable lsp-mode completely. |
This should be better in today's master, we now fuel-limit chalk. |
I'm still seeing the 100% cpu usage on master from this morning, |
That's #1541. |
Same issue here, on 3bdf2e0. Will update with backtrace once I have one |
by defeault we use client-side watching for quite some time I think?
…On Wed, 29 Jan 2020 at 10:54, Laurențiu Nicola ***@***.***> wrote:
@matklad <https://github.com/matklad> should we disable server-side
watching on MacOS? Losing file watching isn't great, but neither are
infinite loops.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2812>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANB3M77K2N7BW3F66CN4IDRAFG4PANCNFSM4KFYFHGA>
.
|
That's only with the Code extension (#2578). |
I'm on
|
It hangs in chalk. By the way you can make the backtrace collapsible by wrapping it in
|
thanks, so it means that rust-analyzer is working properly? right now It responds so slowly that I feel like using plain vim |
No. There are multiple issues open about hanging in Chalk, for example with diesel, but those are bugs. |
Closing this issue as the original bug was fixed. Any other hangs should be reported as new issues. |
With f7a7092, I see one ra_lsp_server process sticking to 100% CPU while using VS Code.
The text was updated successfully, but these errors were encountered: