Open
Bug 1883794
Opened 1 year ago
Updated 11 months ago
Crash in [@ webrender::clip::ClipTree::get_node]
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox125 | --- | affected |
People
(Reporter: release-mgmt-account-bot, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/41feb041-c3e9-4485-b275-417ac0240228
MOZ_CRASH Reason: index out of bounds: the len is 678 but the index is 8388811
Top 10 frames of crashing thread:
0 xul.dll MOZ_Crash mfbt/Assertions.h:301
0 xul.dll RustMozCrash mozglue/static/rust/wrappers.cpp:17
1 xul.dll mozglue_static::panic_hook mozglue/static/rust/lib.rs:96
2 xul.dll core::ops::function::Fn::call<void /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/ops/function.rs:250
3 xul.dll alloc::boxed::impl$49::call library/alloc/src/boxed.rs:2029
3 xul.dll std::panicking::rust_panic_with_hook library/std/src/panicking.rs:783
4 xul.dll std::panicking::begin_panic_handler::closure$0 library/std/src/panicking.rs:657
5 xul.dll std::sys_common::backtrace::__rust_end_short_backtrace<std::panicking::begin_panic_handler::closure_env$0, never$> library/std/src/sys_common/backtrace.rs:171
6 xul.dll std::panicking::begin_panic_handler library/std/src/panicking.rs:645
7 xul.dll core::panicking::panic_fmt library/core/src/panicking.rs:72
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- First crash report: 2024-01-07
- Process type: GPU
- Is startup crash: No
- Has user comments: No
- Is null crash: No
Reporter | ||
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Component: General → Graphics: WebRender
Updated•1 year ago
|
Blocks: gfx-triage
Comment 2•1 year ago
|
||
Low crash volume.
Updated•11 months ago
|
Blocks: wr-stability
You need to log in
before you can comment on or make changes to this bug.
Description
•