Persistent repetition `cargo check` and high CPU consumption

[SpriteOvO]

2026-02-08_19-43-16.mp4

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.

[micisse]

Oh yes, and as soon as I open a RUST project in my IDE, the fun begins... 😅 it started yesterday after upgrade

latest version at the time of writing

[ChayimFriedman2]

@micisse Does this happen on every project? What is your rust-analyzer version? Does rolling rust-analyzer back fixes it?

[SpriteOvO]

For me, this does not happen on a blank cargo new project. But I did encounter this issue two weeks ago in a completely different project on Windows. (OP is about Linux)

[micisse]

@ChayimFriedman2 The problem has been occurring since this most recent version 2026-02-09 (v0.3.2786). I had to switch to 2026-02-02 (v0.3.2777). Also with 2026-02-09 (v0.3.2786), when I run cargo new <fun>, I no longer have the problem. This same project was working correctly until yesterday after upgrading to version v0.3.2786

[ShoyuVanilla]

Do you happen to have a public project where this can be reproduced?

[micisse]

@ShoyuVanilla It's a bit complicated for me. The project is quite large, private with several members and a LOT of files. I'll try to look into it as soon as possible after work. I'll get back to you IF I have any news. For the screenshots below, I've excluded just a few members from the workspace.

2026-02-10_11-v2.mp4

[SpriteOvO]

I tried to minimize it as much as I can, can't go more further.

Cargo.toml

[package]
name = "temp"
version = "0.1.0"
edition = "2024"

[build-dependencies]
shadow-rs = "=1.7.0"

build.rs

use shadow_rs::{BuildPattern::RealTime, ShadowBuilder};

fn main() {
    ShadowBuilder::builder()
        .build_pattern(RealTime)
        .build()
        .unwrap();
}

main.rs

fn main() {
    // Repeat this 2000 lines.
    // It will generate numerous `unused variable` warnings,
    // then you can better observe the `cargo check` time window and high CPU usage.
    let a = 1;
    // ...
}

VSCode settings

    "rust-analyzer.cargo.targetDir": "/tmp/cargo-target-ra",
    "rust-analyzer.server.extraEnv": {
        "RUSTUP_TOOLCHAIN": "nightly"
    },

[ChayimFriedman2]

Should be fixed, if not please reopen.

[SpriteOvO]

Off-topic: @micisse What software is that in your screenshot and video? Looks pretty cool.

[micisse]

@SpriteOvO Yes, one of my favorites (GUI) right now and FOSS 👉 neohtop

[SpriteOvO]

@ChayimFriedman2 This issue is still happened to me, on version

rustc 1.95.0-nightly (1ed488274 2026-02-25)

rust-analyzer version: 1.93.1 (01f6ddf 2026-02-11) [/usr/lib/rustup/bin/rust-analyzer]

I don't have permission of reopening issue in this repo.

[ShoyuVanilla]

Your version doesn't seem to have the fix.
This is the first stable release to include the fix:
https://github.com/rust-lang/rust-analyzer/releases/tag/2026-02-16