Closed Bug 1689956 Opened 4 years ago Closed 4 years ago

Crash in [@ OOM | large | mozalloc_abort | alloc::alloc::__alloc_error_handler::__rg_oom]

Categories

(Core :: General, defect, P1)

Firefox 86
Desktop
Windows
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox86 + wontfix

People

(Reporter: pascalc, Unassigned)

References

Details

(Keywords: crash, regression, regressionwindow-wanted)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/e17483cd-347e-46fb-ab61-fdc320210131

MOZ_CRASH Reason: MOZ_CRASH()

Top 10 frames of crashing thread:

0 mozglue.dll mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33
1 mozglue.dll mozalloc_handle_oom memory/mozalloc/mozalloc_oom.cpp:51
2 xul.dll gkrust_shared::oom_hook::hook toolkit/library/rust/shared/lib.rs:134
3 xul.dll std::alloc::rust_oom ../e1884a8e3c3e813aada8254edfa120e85bf5ffca//library/std/src/alloc.rs:330
4 xul.dll alloc::alloc::__alloc_error_handler::__rg_oom ../e1884a8e3c3e813aada8254edfa120e85bf5ffca//library/alloc/src/alloc.rs:409
5 xul.dll _rust_alloc_error_handler 
6 xul.dll alloc::alloc::handle_alloc_error ../e1884a8e3c3e813aada8254edfa120e85bf5ffca//library/alloc/src/alloc.rs:363
7 xul.dll std::fs::read::inner ../e1884a8e3c3e813aada8254edfa120e85bf5ffca//library/std/src/fs.rs:238
8 xul.dll rkv::backend::impl_safe::environment::{{impl}}::open third_party/rust/rkv/src/backend/impl_safe/environment.rs:121
9 xul.dll cert_storage::make_env security/manager/ssl/cert_storage/src/lib.rs:1064

This new crash signature is spiking up on 86 beta Windows.

Tracking for 86 as the volume is worrisome.

Severity: -- → S1
OS: Windows 10 → Windows
Priority: -- → P1
Hardware: Unspecified → Desktop
Version: unspecified → Firefox 86

Adding a second signature.

Crash Signature: [@ OOM | large | mozalloc_abort | alloc::alloc::__alloc_error_handler::__rg_oom] → [@ OOM | large | mozalloc_abort | alloc::alloc::__alloc_error_handler::__rg_oom] [@ mozalloc_abort | alloc::alloc::__alloc_error_handler::__rg_oom]

Jim, would that fall into your team's bucket?

Flags: needinfo?(jmathies)

For what it is worth, back in the days of e10s rollout, our OOM large crashes only started showing up en masse there, so if there's some similar rollout of WebRender to more platforms there, that could be why this is showing up more.

The signature here is pretty bad. It looks like every OOM crash in all of Rustland is going to be globbed into this. I looked at a few on beta and they were in WebRender, but the crash in comment 0 is in some SSL cert code.

Depends on: 1690034

I filed bug 1690034 about splitting this signature up.

QA Whiteboard: [qa-regression-triage]

Tried to find a regression range, but there is not enough information that could help me reproduce this crash. The QA Whiteboard [qa-regression-triage] is already added, please remove it if this report becomes actionable and QA work is needed.

My guess would be that this is a signature change due to a change in the Rust compiler used in 86, but we'll have to see what shakes out once the Socorro signature changes get deployed.

Bug 1531819 has a bunch of existing WebRender OOMs. Bug 1546671 discusses the general issue of WebRender OOMs.

See Also: → 1531819

These signatures should be gone now.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(jmathies)
Resolution: --- → WORKSFORME

I filed bug 1690386 for the crash in comment 0, though it doesn't appear to be that frequent.

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