-
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
100% cpu usage #1541
Comments
Oh yeah, I've seen that, too. Leave some VSCode windows open for and suddenly my Macbook gets loud. I swear I've also killed a few zombie ra_lsps that were left over from already closed editors. No idea how to reproduce this, though. |
It would be invaluable to get a stack trace from a hang up ra_lsp |
Tell me how to get that from a running process on macos and I'll get you one next time I see this :)
… Am 18.07.2019 um 14:02 schrieb Aleksey Kladov ***@***.***>:
It would be invaluable to get a stack trace from a hang up ra_lsp
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I think |
Got it again. Tried to attach with lldb but it failed and closed the process:
|
@max-frai are you sure the process exitted? Stopping just means that the process is paused, so that you can inspect the current state. If it was just stopped, can you run |
You are right:
|
Could you please run
to get a backtrace for every thread. |
Sorry, had to kill the process because my notebook started lagging. Will do this next time I catch this bug. |
Got a live one! I closed a VSCode window and ra_lsp didn't exit. bt all
|
Reported upstream: notify-rs/notify#208 |
I get this every time I try to use vscode+ra on rustc itself on a Mac. Same setup works fine on a Linux machine. |
I get it as well, on a Mac. Unfortunately, it looks like the upstream issue hasn't gotten a lot of attention. I'll embed my backtrace, in case it can shed some more light on this. backtrace
|
@JeanMertz I'm pretty sure that's #1684 / #1744, not this one (you can tell from |
Notify side of the problem should be worked-around by #1780 |
Closing the issue: I consider the notify side fixed by #1780 (although, long term, we need some better watching solution), and the chalk issues are tracked elsewhere |
Sometimes ra_lsp process stuck in infinite 100% cpu usage even on small project and after it's fully loaded. I use latest commit.
Sometimes I close notebook at night and go to sleep, and after wake up I see that notebook is very hot and didn't sleep because of ra_lsp.
The text was updated successfully, but these errors were encountered: