Closed Bug 1978076 Opened 1 year ago Closed 1 year ago

Crash in [@ wgpu_core::storage::Storage<T>::insert]

Categories

(Core :: Graphics: WebGPU, defect)

defect

Tracking

()

RESOLVED FIXED
142 Branch
Tracking Status
firefox-esr128 --- unaffected
firefox-esr140 --- unaffected
firefox140 --- unaffected
firefox141 --- unaffected
firefox142 blocking fixed

People

(Reporter: diannaS, Unassigned)

References

(Regression)

Details

(Keywords: crash, regression)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/c26b924a-3e4b-4b3f-a56f-a0e210250718

MOZ_CRASH Reason:

assertion `left != right` failed: Index 0 of Device is already occupied
  left: 1
 right: 1

Top 10 frames:

0  libxul.so  MOZ_CrashSequence(void*, long)  mfbt/Assertions.h:248
0  libxul.so  MOZ_Crash(char const*, int, char const*)  mfbt/Assertions.h:381
0  libxul.so  RustMozCrash  mozglue/static/rust/wrappers.cpp:18
1  libxul.so  mozglue_static::panic_hook  mozglue/static/rust/lib.rs:99
2  libxul.so  core::ops::function::Fn::call  /builds/worker/fetches/rustc/lib/rustlib/src/rust/library/core/src/ops/function.rs:79
3  libxul.so  <alloc::boxed::Box<F, A> as core::ops::function::Fn<Args>>::call  library/alloc/src/boxed.rs:1990
3  libxul.so  std::panicking::rust_panic_with_hook  library/std/src/panicking.rs:839
4  libxul.so  std::panicking::begin_panic_handler::{{closure}}  library/std/src/panicking.rs:704
5  libxul.so  std::sys::backtrace::__rust_end_short_backtrace  library/std/src/sys/backtrace.rs:168
6  libxul.so  rust_begin_unwind  library/std/src/panicking.rs:695

:aleiserson could this be related to bug 1976958? If so, should we back it out of nightly?

Flags: needinfo?(aleiserson)

I can reproduce this consistently with:

  • docker run -p 3001:3000 --name=grafana grafana/grafana-enterprise
  • going to 127.0.0.1:3001
  • logging in (admin/admin)
  • trying to create a dashboard

I discovered this while trying to open one of grafana's selector on a dashboard but apparently creating one triggers the assertion too.

Setting dom.webgpu.enabled to false "fixes" the issue.

Yes, it seems likely that bug 1976958 is the cause and should be backed out.

Flags: needinfo?(aleiserson)
Keywords: regression
Regressed by: 1976958

Set release status flags based on info from the regressing bug 1976958

Marking as fixed because bug 1976958 was backed out of central. Waiting on new nightlies.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 142 Branch
Duplicate of this bug: 1978069
See Also: → 1978107
QA Whiteboard: [qa-triage-done-c143/b142]
You need to log in before you can comment on or make changes to this bug.