Open Bug 1864687 Opened 2 years ago Updated 1 year ago

Crash in [@ webrender::renderer::upload::UploadTexturePool::format_index]

Categories

(Core :: Graphics: WebRender, defect)

Unspecified
Windows
defect

Tracking

()

Tracking Status
firefox-esr115 --- affected
firefox119 --- wontfix
firefox120 --- affected
firefox121 --- affected

People

(Reporter: aryx, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

This crash signature has been observed for some time but got more frequent for Nightly 121.0a1 with 29 crashes from 20 installations starting with build ID 20231106094018.

Crash report: https://crash-stats.mozilla.org/report/index/6b274cce-ba5e-489d-afea-a94470231114

MOZ_CRASH Reason: unexpected format

Top 10 frames of crashing thread:

0  xul.dll  MOZ_Crash  mfbt/Assertions.h:281
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/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/ops/function.rs:250
3  xul.dll  alloc::boxed::impl$49::call  library/alloc/src/boxed.rs:2021
3  xul.dll  std::panicking::rust_panic_with_hook  library/std/src/panicking.rs:711
4  xul.dll  std::panicking::begin_panic::closure$0<ref$<str$> >  /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:628
5  xul.dll  std::sys_common::backtrace::__rust_end_short_backtrace<std::panicking::begin_panic::closure_env$0<ref$<str$> >, never$>  /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:170
6  xul.dll  std::panicking::begin_panic<ref$<str$> >  /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:627
7  xul.dll  webrender::renderer::upload::UploadTexturePool::format_index  gfx/wr/webrender/src/renderer/upload.rs:663

Glenn, do you have an idea what started this? First affected build is from a Monday, regressing change could have landed the previous days.

Flags: needinfo?(gwatson)

No, I'm not sure what could cause that - Nical might have some ideas?

Flags: needinfo?(gwatson) → needinfo?(nical.bugzilla)
Severity: -- → S3

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

  • Top 10 desktop browser crashes on nightly

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

For more information, please visit BugBot documentation.

Flags: needinfo?(gwatson)
Keywords: topcrash

We could probably make the assert provide some more information, that may offer a clue to what's happening, but it's likely we will still need a local repro to understand this properly.

Severity: S3 → S2
Flags: needinfo?(gwatson)
Blocks: wr-stability

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.

Keywords: topcrash

Bug 1883932 has a reproducible testcase (and a possible regressor)

See Also: → 1883932

mid-level gpu process crash which we recover from. Still S2? We do have a test case now, so might be more actionable.

Blocks: gfx-triage

This was likely fixed in bug 1883932.

Flags: needinfo?(nical.bugzilla)
No longer blocks: gfx-triage

Since the crash volume is low (less than 15 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit BugBot documentation.

Severity: S2 → S3
You need to log in before you can comment on or make changes to this bug.