Open Bug 1760022 Opened 2 years ago Updated 2 years ago

Windows 32-bit Crash in [@ OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain]

Categories

(Core :: Graphics: Layers, defect)

x86
Windows
defect

Tracking

()

People

(Reporter: aryx, Unassigned)

Details

(Keywords: crash)

Crash Data

Only on Windows with 32-bit builds, crash reports start with version 99, didn't find an old related signature. 44 content crashes for v99 Nightly and Beta so far.

Crash report: https://crash-stats.mozilla.org/report/index/b51131b9-0201-4c6e-85b6-6eb1f0220317

MOZ_CRASH Reason: out of memory: 0x000000000006FB9E bytes requested

Top 10 frames of crashing thread:

0 mozglue.dll mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:26
1 mozglue.dll mozalloc_handle_oom memory/mozalloc/mozalloc_oom.cpp:51
2 xul.dll mozglue_static::oom_hook::hook mozglue/static/rust/lib.rs:115
3 xul.dll std::alloc::rust_oom ../9d1b2106e23b1abd32fce1f17267604a5102f57a//library/std/src/alloc.rs:329
4 xul.dll alloc::alloc::__alloc_error_handler::__rg_oom ../9d1b2106e23b1abd32fce1f17267604a5102f57a//library/alloc/src/alloc.rs:413
5 xul.dll __rust_alloc_error_handler 
6 xul.dll mozilla::layers::ClipManager::DefineClipChain gfx/layers/wr/ClipManager.cpp:404
7 xul.dll mozilla::layers::ClipManager::SwitchItem gfx/layers/wr/ClipManager.cpp:233
8 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList gfx/layers/wr/WebRenderCommandBuilder.cpp:1913
9 xul.dll mozilla::nsDisplayOwnLayer::CreateWebRenderCommands layout/painting/nsDisplayList.cpp:5281
Crash Signature: [@ OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain] → [@ OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain][OOM | large | mozalloc_abort | mozilla::wr::DisplayListBuilder::DefineClipChain][OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain]
Crash Signature: [@ OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain][OOM | large | mozalloc_abort | mozilla::wr::DisplayListBuilder::DefineClipChain][OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain] → [@ OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain][@ OOM | large | mozalloc_abort | mozilla::wr::DisplayListBuilder::DefineClipChain][@ OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain]
Crash Signature: [@ OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain][@ OOM | large | mozalloc_abort | mozilla::wr::DisplayListBuilder::DefineClipChain][@ OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain] → [@ OOM | large | mozalloc_abort | mozilla::layers::ClipManager::DefineClipChain][@ OOM | large | mozalloc_abort | mozilla::wr::DisplayListBuilder::DefineClipChain]
Severity: S2 → S3

This seems to be happening a bunch on https://www.betking.com

Browsed around on that website a bit (without logging in), I never saw a clip chain length over 20, which is the only thing that looked like it could cause us to make a large allocation with that stack.

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