thread '<unnamed>' panicked at 'Forcing query with already existing DepNode.

[bjorn3]

thread '<unnamed>' panicked at 'Forcing query with already existing DepNode.
- query-key: Canonical { variables: [CanonicalVarInfo { kind: Region }], value: ParamEnvAnd { param_env: ParamEnv { caller_bounds: [], reveal: UserFacing }, value: Binder(TraitPredicate(<std::collections::hash::table::RawTable<rustc_mir::monomorphize::MonoItem<'_>, ()> as std::marker::Copy>)) } }
- dep-node: EvaluateObligation(bb5cec2cf56c93bb-77a4f4dd8fa6aff4)', librustc/ty/query/plumbing.rs:531:9
note: Run with `RUST_BACKTRACE=1` for a backtrace.

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: rustc 1.30.0-nightly (33b923fd4 2018-08-18) running on x86_64-unknown-linux-gnu

thread '<unnamed>' panicked at 'Forcing query with already existing DepNode.
- query-key: Canonical { variables: [CanonicalVarInfo { kind: Region }, CanonicalVarInfo { kind: Region }, CanonicalVarInfo { kind: Region }], value: ParamEnvAnd { param_env: ParamEnv { caller_bounds: [Binder(TraitPredicate(<impl Backend as cranelift_module::Backend>)), Binder(TraitPredicate(<impl Backend as std::marker::Sized>)), Binder(OutlivesPredicate('?0, '?1))], reveal: UserFacing }, value: Binder(TraitPredicate(<&cranelift::cranelift_codegen::ir::Layout as std::marker::Copy>)) } }
- dep-node: EvaluateObligation(e614cce79f0ae9bb-1f88ba4989df1277)', librustc/ty/query/plumbing.rs:531:9

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: rustc 1.30.0-nightly (33b923fd4 2018-08-18) running on x86_64-unknown-linux-gnu

thread '<unnamed>' panicked at 'Forcing query with already existing DepNode.
- query-key: Canonical { variables: [], value: ParamEnvAnd { param_env: ParamEnv { caller_bounds: [], reveal: UserFacing }, value: Binder(TraitPredicate(<std::vec::Vec<cranelift_module::module::ModuleFunction<cranelift_faerie::FaerieBackend>> as std::marker::Copy>)) } }
- dep-node: EvaluateObligation(c30dea39a4e39c58-7978eb017786dc74)', librustc/ty/query/plumbing.rs:531:9

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: rustc 1.30.0-nightly (33b923fd4 2018-08-18) running on x86_64-unknown-linux-gnu

[jens1o]

error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

I would say you are reporting this at the wrong repo

[bjorn3]

I thought it could be related to how rls uses rustc.

[jens1o]

Okay, that is a valid point. Let's wait until one of the devs bring up this issue.

[nrc]

cc @michaelwoerister

@bjorn3 do you have the source code you were working with?

[michaelwoerister]

Possibly related to rust-lang/rust#49300

[bjorn3]

do you have the source code you were working with?

No, not the source at the moment of the crash, because I noticed it only after some changes didn't give inline errors.

[braden]

This is happening to me as well, if I clear /target/rls and restart rls it will work once but then breaks on a random type when I change anything.

The VSCode extension also shows these warnings, again with random types each time:
#0 [needs_drop_raw] computing whether 'math::Matrix3' needs drop
#1 [rvalue_promotable_map] checking which parts of 'ui::UI::new' are promotable to static
#2 [const_is_rvalue_promotable_to_static] const checking if rvalue is promotable to static 'ui::UI::new'

[nrc]

@braden do you have a project which reproduces this error?

[braden]

The project is not public unfortunately, but let me know if there is something I can do to help diagnose the problem.

[nrc]

@bjorn3 @braden does this still reproduce (with the next nightly with the RLS, there is currently no RLS). I landed a patch which might address this.

[bjorn3]

I haven't seen this since I reported it, so I don't know if the bug still exists.

[davidcornu]

I can confirm this is still happening on rustc 1.31.0-nightly (96064eb61 2018-10-28) running on x86_64-apple-darwin. I haven't been able to narrow it down to a specific set of actions but it's happened twice in close succession.

[michaelwoerister]

Maybe @nikomatsakis knows how two evaluate_obligation query-keys could end up being mapped to the same dep-node?