You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few days ago, rust-analyzer started behaving a bit weird and taking longer than usual. Today it's been crashing nonstop all day, I even uninstalled everything and re-installed with rustup, and the behavior persisted. At one point today every character I typed caused another worker thread panic message.
I have tried to create a minimum reproducible example, but this odd behavior seems to follows no God, much less listens to mortals. I am using VS Code, I've tried adding "rust-analyzer.trace.server": "verbose" and "rust-analyzer.cargo.extraEnv": {"RA_LOG": "info", "RUST_BACKTRACE": "full" } to settings.json but even after a restart this seemed to have no effect. Still, I have captured the stderr output into a file here.
This file holds the output of around an hour of usage. It seems to be particularly angry about me using the Result enum, multiple of the crashes were when typing Result::something.
If there's anything else I can provide to help, do let me know! Thank you! 😊
A few days ago, rust-analyzer started behaving a bit weird and taking longer than usual. Today it's been crashing nonstop all day, I even uninstalled everything and re-installed with rustup, and the behavior persisted. At one point today every character I typed caused another worker thread panic message.
I have tried to create a minimum reproducible example, but this odd behavior seems to follows no God, much less listens to mortals. I am using VS Code, I've tried adding
"rust-analyzer.trace.server": "verbose"
and"rust-analyzer.cargo.extraEnv": {"RA_LOG": "info", "RUST_BACKTRACE": "full" }
tosettings.json
but even after a restart this seemed to have no effect. Still, I have captured the stderr output into a file here.This file holds the output of around an hour of usage. It seems to be particularly angry about me using the
Result
enum, multiple of the crashes were when typingResult::
something.If there's anything else I can provide to help, do let me know! Thank you! 😊
rustc version: 1.76.0 (07dca489a 2024-02-04)
rust-analyzer version: 0.3.1860-standalone (5346002 2024-02-25)
The text was updated successfully, but these errors were encountered: