1898322 - Crash in [@ core::option::expect_failed | webrender::clip::ClipTreeBuilder::clip_chain_has_complex_clips]

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebRender, defect)

Description

[Liz Henry (:lizzard)]

There's a cluster of newly spiking signatures that look related, in Nightly 128.
Maybe this is fallout from fixing the high volume crash in bug 1896979.

Crash report: https://crash-stats.mozilla.org/report/index/d48ca4e8-206e-4feb-b423-6000c0240522

MOZ_CRASH Reason: no entry found for key

Top 10 frames:

0  xul.dll  MOZ_Crash(char const*, int, char const*)  mfbt/Assertions.h:317
0  xul.dll  RustMozCrash(char const*, int, char const*)  mozglue/static/rust/wrappers.cpp:18
1  xul.dll  mozglue_static::panic_hook(core::panic::panic_info::PanicInfo*)  mozglue/static/rust/lib.rs:98
2  xul.dll  core::ops::function::Fn::call<void (*)(ref$<core::panic::panic_info::PanicInf...  /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/core/src/ops/function.rs:250
3  xul.dll  alloc::boxed::impl$49::call()  library/alloc/src/boxed.rs:2034
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_...  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

Comment 1

[Jeff Muizelaar [:jrmuizel]]

These signatures are very unlikely to share the same underlying cause. Can we have separate bugs for them?

Comment 2

[Liz Henry (:lizzard)]

OK, no problem!

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.

For more information, please visit BugBot documentation.

Comment 4

[Sotaro Ikeda [:sotaro]]

:nical, can you comment to the bug?

Comment 5

[Nicolas Silva [:nical]]

The panic is happening in scene building which is before all of the quad-related code gets to run so it can't be related to bug 1896979. It looks like an invalid clip chain ID is used on a stacking context, the issue manifests during scene building but the error is probably actually happening when building the display list on the content process.

It's not a very high crash volume and without some way to reproduce it's going to be hard to track down.

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.