Repository navigation
A dep graph node (mir_drops_elaborated_and_const_checked) does not have an unique index #141540
Description
Activity
- addedI-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.C-bugCategory: This is a bug.Category: This is a bug.
on May 25, 2025 - addedneeds-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triagingThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
on May 25, 2025 - addedA-query-systemArea: The rustc query system (https://rustc-dev-guide.rust-lang.org/query.html)Area: The rustc query system (https://rustc-dev-guide.rust-lang.org/query.html)A-incr-compArea: Incremental compilationArea: Incremental compilationand removedneeds-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triagingThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
on Jun 1, 2025 The same for me. It's really frustrating. A
cargo cleansometimes fixes it but it randomly comes back. @dfaust did you ever figure it out?@nastynaz I disabled incremental compilation. No issues since.
Reacted by Naz- marked Using
#[allow(dead_code)]instead of#[allow(unused)]spuriously crashes the nightly compiler #142206 as a duplicate of this issueon Jun 10, 2025 This was the only thing that fixed it for me. Thanks for sharing. It's slightly annoying having longer compile times but better than the previous flakiness. Out of curiosity, are you using
#![feature(generic_const_exprs)]anywhere in your code? The compiler had an issue with this in the past that was supposedly fixed and I wonder whether it's the same bug cropping up in a different form.- addedS-needs-reproStatus: This issue has no reproduction and needs a reproduction to make progress.Status: This issue has no reproduction and needs a reproduction to make progress.
on Jun 11, 2025 hey, still hapenning as of 2025, June 12.
personally it happens when multiples cargo commands are running at the same time (waiting for file lock on package cache). there might a be problem synchronization problem on the cache. of course after cargo clean everything is back to workingI'm seeing this multiple times per hour while working on this Turbopack: https://github.com/vercel/next.js/tree/canary/turbopack/crates which does use a number of nightly features, but not
generic_const_exprs.
I have no simple way to reproduce this, but it does always eventually happen after changing code and compiling often enough.27 remaining items
- added a commit that references this issue
on Dec 13, 2025 Issue debugged, a solution is proposed in #150156.
Reacted by jasper, Daniel Faust and Finchie- added a commit that references this issue
on Dec 21, 2025 - added a commit that references this issue
on Dec 29, 2025 So this particular bug might be fixed now, I haven't seen it for days. (on 2026-01-03)
It feels like the compiler crashes just as often though, but instead with different error messages: #150018 (comment)
Reacted by TeamDman and Daniel Faust- added 2 commits that reference this issue
on Feb 10, 2026 - added 4 commits that reference this issue
on Feb 13, 2026 - added a commit that references this issue
on Aug 7, 2026
The error has been occurring sporadically for like a week or two with recent nightly versions. Unfortunately I don't have more details, please let me know if I can help somehow.
Error output
Work-around
You can disable incremental compilation to avoid this issue.
There are multiple ways to do it, for example:
Add this to
$WORKSPACE/.cargo/config.toml:or set the
CARGO_INCREMENTALenvironment variable:export CARGO_INCREMENTAL=0