-
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
Rust-analyzer hangs on file with cyclic traits #12897
Labels
A-ty
type system / type inference / traits / method resolution
C-bug
Category: bug
S-actionable
Someone could pick this issue up and work on it right now
Comments
lnicola
added
S-actionable
Someone could pick this issue up and work on it right now
C-bug
Category: bug
labels
Jul 28, 2022
Seems to happen only to the recursive solver. Reproduced as chalk test in rust-lang/chalk#773 |
Is there a way to work around this? this is preventing me from using rust-analyzer entirely. |
Merged
bors
added a commit
that referenced
this issue
Dec 5, 2022
Update to Chalk 88 This Chalk release introduces fuel for the recursive solver ([chalk#774](rust-lang/chalk#774)). I'm not sure how often it calls `should_continue` compared to the other solver, so we might want to increase `CHALK_SOLVER_FUEL`, the current default value of 100 might be too low. This should fix a lot of hangs and crashes, for example this solves the hang in #12897.
Fixed on master, now that we're using Chalk solver fuel again. |
Well, worked around 😅 the bug is still there... |
We can still close this on our side though, no? Since it is tracked upstream with an issue. |
Agreed, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-ty
type system / type inference / traits / method resolution
C-bug
Category: bug
S-actionable
Someone could pick this issue up and work on it right now
rust-analyzer version: rust-analyzer 0.4.1143-standalone (4087535 2022-07-27)
rustc version: rustc 1.62.1 (e092d0b6b 2022-07-16)
Reproduction
src/main.rs
by the followingrust-analyzer analysis-stats .
Result
rust-analyzer outputs
and then hangs, continuing to use 100% of one CPU core.
Stack trace
Here's the output of a stack trace generated by gdb for the hanging process:
The text was updated successfully, but these errors were encountered: