1782001 - Crash in [@ core::option::expect_failed | webrender::clip::ClipTreeBuilder::build_clip_set]

Status: REOPENED

(Core :: Graphics: WebRender, defect)

Description

[Calixte Denizet (:calixte)]

Crash report: https://crash-stats.mozilla.org/report/index/c2afef1f-d6eb-4a68-8821-a55340220728

MOZ_CRASH Reason: no entry found for key

Top 10 frames of crashing thread:

0 xul.dll RustMozCrash mozglue/static/rust/wrappers.cpp:17
1 xul.dll mozglue_static::panic_hook mozglue/static/rust/lib.rs:91
2 xul.dll core::ops::function::Fn::call<void  ../a8314ef7d0ec7b75c336af2c9857bfaf43002bfc/library/core/src/ops/function.rs:248
3 xul.dll std::panicking::rust_panic_with_hook library/std/src/panicking.rs:702
4 xul.dll std::panicking::begin_panic_handler::closure$0 library/std/src/panicking.rs:588
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:138
6 xul.dll std::panicking::begin_panic_handler library/std/src/panicking.rs:584
7 xul.dll core::panicking::panic_fmt library/core/src/panicking.rs:142
8 xul.dll core::panicking::panic_display<str> library/core/src/panicking.rs:72
9 xul.dll core::panicking::panic_str library/core/src/panicking.rs:56

There is 1 crash in nightly 105 with buildid 20220727093731. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1779952.

[1] https://hg.mozilla.org/mozilla-central/rev?node=7016bef75f07

Comment 1

[Glenn Watson [:gw]]

I can't reproduce this on the reported URL, and it looks like there's been a single crash so far - so not really actionable for now. Will keep an eye on this though, as it seems like the kind of crash that could occur on other pages too.

Comment 2

[Taddes Korris [:taddes]]

Hi Glenn. Just checking to see if the Sev 2 should remain for this, given there has only been a single crash.

Comment 3

[Glenn Watson [:gw]]

There are four crashes in total now, but it's still unactionable for now as I can't repro locally with any of the provided crash URLs . So yes, I think it can be dropped to S3.

Comment 4

[Glenn Watson [:gw]]

This seems to have been resolved now - there are no recent crashes.

Comment 5

[Jeff Muizelaar [:jrmuizel]]

This is back: https://crash-stats.mozilla.org/report/index/f972667d-bc82-4ec6-a157-f19f50220914
I think it just went away because of a signature change

Comment 6

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

The bug is linked to a topcrash signature, which matches the following criterion:

• Top 5 GPU process crashes on release

:gw, could you consider increasing the severity of this top-crash bug?

For more information, please visit BugBot documentation.

Comment 7

[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.