Open Bug 1718356 Opened 3 months ago Updated 3 months ago

Crash in [@ OOM | large | mozalloc_abort | alloc::raw_vec::{{impl}}::reserve::do_reserve_and_handle<T>]

Categories

(Core :: Graphics: WebRender, defect)

x86_64
Windows
defect

Tracking

()

Tracking Status
firefox-esr78 --- unaffected
firefox89 --- unaffected
firefox90 --- unaffected
firefox91 --- affected

People

(Reporter: mccr8, Unassigned)

Details

(Keywords: crash, Whiteboard: [not-a-fission-bug])

Crash Data

Maybe Fission related. (DOMFissionEnabled=1)

Crash report: https://crash-stats.mozilla.org/report/index/f36b21b4-d5fc-43c9-a011-78a7c0210619

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 ../53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b//library/std/src/alloc.rs:331
4 xul.dll alloc::alloc::__alloc_error_handler::__rg_oom ../53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b//library/alloc/src/alloc.rs:397
5 xul.dll _rust_alloc_error_handler 
6 xul.dll alloc::alloc::handle_alloc_error ../53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b//library/alloc/src/alloc.rs:366
7 xul.dll alloc::raw_vec::{{impl}}::reserve::do_reserve_and_handle<webrender::hit_test::HitTestClipNode, alloc::alloc::Global> ../53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/alloc/src/raw_vec.rs:325
8 xul.dll webrender::hit_test::add_clips gfx/wr/webrender/src/hit_test.rs:519
9 xul.dll webrender::scene_building::SceneBuilder::build_item gfx/wr/webrender/src/scene_building.rs:1182

Looks like a WebRender OOM that showed up in the 20210618092056 build. I'm assuming that it is probably a signature shift, but who knows maybe it isn't.

Severity: -- → S2

Looks like a WebRender OOM that showed up in the 20210618092056 build. I'm assuming that it is probably a signature shift, but who knows maybe it isn't.

Here's the changelog for build 20210618092056:

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2f69dc403886dd1c721cec815b00ec5bfca4b393&tochange=d70c3d846c395717c429cd3f3433457f5f92dced

There were four WebRender changes in that build:

Bug 1715515 - Part 1. Switch Windows 32 and mingwclang tests to WebRender.
Bug 1459526 - Handle full-range video in Webrender.
Bug 1717028 - Fix webrender render target debug view.
Bug 1716971 - Enable webrender on Android on NVIDIA Tegra GPUs.

All of these crashes are on Windows, so the Android bug is probably not relevant. All of these crashes are on amd64, so the Windows 32-bit test bug is probably not relevant.

There is also a bug related to graphics memory pressure, which might be related since this bug is about WebRender OOMs:

Bug 1716579 - Minimize memory usage of windows that haven't been rendered for a long time. r=gfx-reviewers,bradwerth

OS: Windows 10 → Windows
Hardware: Unspecified → x86_64

This doesn't look like a Fission crash even though the crash report in comment 0 has DOMFissionEnabled=1. Adding [not-a-fission-bug] whiteboard tag to hide this bug from Fission bug triage queries.

Whiteboard: [not-a-fission-bug]
You need to log in before you can comment on or make changes to this bug.