rust-lang / rust-lang/rust-analyzer
Persistent repetition `cargo check` and high CPU consumption
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
https://github.com/user-attachments/assets/a1f6e96c-120e-489b-be63-f235f6e19e76
rust-analyzer version: rust-analyzer version: 0.3.2777-standalone [~/.vscode/extensions/rust-lang.rust-analyzer-0.3.2777-linux-x64/server/rust-analyzer]
rustc version: rustc 1.95.0-nightly (c7f5f3e0d 2026-02-07)
editor or extension: VSCode 0.3.2777
relevant settings:
Removing any one of the settings no longer produces the issue.
"rust-analyzer.cargo.targetDir": "/tmp/cargo-target-ra",
"rust-analyzer.server.extraEnv": {
"RUSTUP_TOOLCHAIN": "nightly"
},
repository link (if public, optional): closely at dev branch
code snippet to reproduce: Let me know if you need more minimal reproducible code snippet besides the repo above.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the linked closely repository on its dev branch with the listed rust-analyzer and rustc versions. Start by testing the two relevant settings together and observe the repeated cargo check and CPU usage. Done means identifying the trigger and preventing the repetition and high CPU consumption without removing either setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100