Open Bug 1843348 Opened 2 years ago Updated 8 months ago

Crash in [@ core::result::unwrap_failed | webrender::renderer::upload::copy_into_staging_buffer]

Categories

(Core :: Graphics: WebRender, defect, P2)

Unspecified
Windows 11
defect

Tracking

()

Tracking Status
firefox141 + wontfix
firefox142 + wontfix

People

(Reporter: RyanVM, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

All crashes are from Windows 11.

Crash report: https://crash-stats.mozilla.org/report/index/2f4f004c-ca6c-4afb-9636-f44a70230713

MOZ_CRASH Reason: called `Result::unwrap()` on an `Err` value: "Failed to transiently map PBO of size 1048576 bytes"

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/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/ops/function.rs:166
3  xul.dll  alloc::boxed::impl$47::call  library/alloc/src/boxed.rs:2001
3  xul.dll  std::panicking::rust_panic_with_hook  library/std/src/panicking.rs:696
4  xul.dll  std::panicking::begin_panic_handler::closure$0  library/std/src/panicking.rs:583
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:150
6  xul.dll  std::panicking::begin_panic_handler  library/std/src/panicking.rs:579
7  xul.dll  core::panicking::panic_fmt  library/core/src/panicking.rs:64

Not a high crash volume, and doesn't seem exploitable, so setting to S3. Glenn, please adjust if you feel a different level is required.

Severity: -- → S3
Priority: -- → P2

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
Flags: needinfo?(gwatson)

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

The bug is marked as tracked for firefox141 (beta) and tracked for firefox142 (nightly). However, the bug still isn't assigned and has low severity.

:bhood, could you please find an assignee and increase the severity for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Flags: needinfo?(bhood)

This is a reminder regarding comment #4!

The bug is marked as tracked for firefox141 (beta) and tracked for firefox142 (nightly). We have limited time to fix this, the soft freeze is in 14 days. However, the bug still isn't assigned.

The immense spike here appears to be coming from a single user with crash auto-submit enabled and a GPU process that keeps crashing over and over.

This is a reminder regarding comment #4!

The bug is marked as tracked for firefox141 (beta) and tracked for firefox142 (nightly). We have limited time to fix this, the soft freeze is in 8 days. However, the bug still isn't assigned.

This is a reminder regarding comment #4!

The bug is marked as tracked for firefox141 (beta) and tracked for firefox142 (nightly). We have limited time to fix this, the soft freeze is in 2 days. However, the bug still isn't assigned.

20250721090929 was the last nightly with the crash, and 20250721154325 was the first nightly without. I don't see anything obvious that would have changed it in the pushlog though:
https://hg-edge.mozilla.org/mozilla-central/pushloghtml?fromchange=9396a65ed903&tochange=bca22a6d040254394460927eef891c3c01434123

I guess the user switched to beta?

This is a reminder regarding comment #4!

The bug is marked as tracked for firefox141 (release) and tracked for firefox142 (beta). We have limited time to fix this, the soft freeze is in 14 days. However, the bug still isn't assigned.

This is a reminder regarding comment #4!

The bug is marked as tracked for firefox141 (release) and tracked for firefox142 (beta). We have limited time to fix this, the soft freeze is in 8 days. However, the bug still isn't assigned.

You need to log in before you can comment on or make changes to this bug.