Closed
Bug 1861937
Opened 1 year ago
Closed 11 months ago
Crash in [@ wgpu_core::storage::Storage<T>::get] with RenderPipeline[0] does not exist
Categories
(Core :: Graphics: WebGPU, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gsvelto, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/d7afcbf5-d9e1-493c-adf2-836180231028
MOZ_CRASH Reason: RenderPipeline[0] does not exist
Top 10 frames of crashing thread:
0 libxul.so MOZ_Crash mfbt/Assertions.h:281
0 libxul.so RustMozCrash mozglue/static/rust/wrappers.cpp:18
1 libxul.so mozglue_static::panic_hook mozglue/static/rust/lib.rs:96
2 libxul.so core::ops::function::Fn::call 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:2007
3 libxul.so std::panicking::rust_panic_with_hook library/std/src/panicking.rs:709
4 libxul.so std::panicking::begin_panic_handler::{{closure}} library/std/src/panicking.rs:597
5 libxul.so std::sys_common::backtrace::__rust_end_short_backtrace library/std/src/sys_common/backtrace.rs:151
6 libxul.so rust_begin_unwind library/std/src/panicking.rs:593
7 libxul.so core::panicking::panic_fmt library/core/src/panicking.rs:67
Low-volume nightly-only crash, this might have been introduced by bug 1859999. Teodor, can you have a look please?
Updated•1 year ago
|
Comment 1•1 year ago
|
||
This looks related to BGL deduplication. Nical, could you take a look?
Flags: needinfo?(nical.bugzilla)
Comment 2•1 year ago
|
||
It's a missing pipeline so probably unrelated. We'll prioritize it if the crash volume is important.
Flags: needinfo?(nical.bugzilla)
Comment 3•11 months ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → WORKSFORME
Updated•3 months ago
|
Summary: Crash in [@ wgpu_core::storage::Storage<T>::get] → Crash in [@ wgpu_core::storage::Storage<T>::get] with RenderPipeline[0] does not exist
You need to log in
before you can comment on or make changes to this bug.
Description
•