Thunderbird Crash in [@ OOM | large | mozalloc_abort | xul.dll | webrender::renderer::Renderer::render_impl]
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: wsmwk, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, topcrash-thunderbird)
Crash Data
#19 crash for Thunderbird 102.5.1
Crash report: https://crash-stats.mozilla.org/report/index/f72d9dc7-30e7-4371-b309-194f10221219
MOZ_CRASH Reason: out of memory: 0x0000000000100000 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 ../7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c//library/std/src/alloc.rs:329
4 xul.dll alloc::alloc::__alloc_error_handler::__rg_oom ../7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c//library/alloc/src/alloc.rs:411
5 xul.dll xul.dll@0x3d36724
6 xul.dll webrender::renderer::Renderer::render_impl gfx/wr/webrender/src/renderer/mod.rs:1975
7 xul.dll webrender_bindings::bindings::wr_renderer_render gfx/webrender_bindings/src/bindings.rs:616
8 xul.dll mozilla::wr::RendererOGL::UpdateAndRender gfx/webrender_bindings/RendererOGL.cpp:185
9 xul.dll mozilla::wr::RenderThread::UpdateAndRender gfx/webrender_bindings/RenderThread.cpp:537
FWIW, faulty AMD hardware is suggested for Bug 1738381 - Crash in [@ OOM | large | mozalloc_abort | webrender::renderer::Renderer::render_impl]
Reporter | ||
Comment 1•8 months ago
|
||
On Tuesday Oct 24, in the range of 115.3.3/115.4.1 (115.4.0 was skipped) the rate of crashes doubled.
Reporter | ||
Comment 2•8 months ago
|
||
so, perhaps some regression was introduced. There are no useful crash comments
bp-4f349c50-df6c-4181-ae9e-3b9e60231112 (not startup)
bp-a0509dc0-3bb0-491a-b094-e5c890231112 (startup)
Comment 3•8 months ago
|
||
Nothing likely from comm code. https://hg.mozilla.org/releases/comm-esr115/pushloghtml?fromchange=THUNDERBIRD_115_3_3_RELEASE&tochange=THUNDERBIRD_115_4_1_RELEASE
Reporter | ||
Updated•4 months ago
|
Comment 4•4 months ago
|
||
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.
Reporter | ||
Comment 6•4 months ago
|
||
Signature changed.
Still a top 10crash for Thunderbird 115.8.1.
Reporter | ||
Comment 7•3 months ago
|
||
All 3 of these refer to composing an email:
- bp-4dfea5d1-f0e2-4eb6-b7c7-79fe90240307
- bp-1152ffff-3a78-4eb9-a52f-557430240322
- bp-03137eb7-420e-4793-b82e-3c9ca0240310
All 3 of these crashes have 2gb virtual. And 61% of Thunderbird crashes with signature webrender::renderer::Renderer::render_impl are 2g virtual but only 5% of the overall Thunderbird user population are running with 2gb. Perhaps suggests 2gb is insufficient minimum specs to be running version 115?
Or is there a render bug?
4gb virtual crashes:
- bp-6cc2fd38-1298-4b30-b6a3-aad850240323 36 minutes
- bp-f22fa4e6-f4b7-4d99-a3ba-52fdb0240323 85 seconds
- bp-7a8b3f5d-7cb4-4b44-9c80-3d6270240318 6 minutes
Comment 8•3 months ago
|
||
Is there any way we can get an about:memory
report from a system experiencing this prior to OOM? It's possible there is a memory leak, though it's more likely just a general OOM issue that happens to hit in WR rather than WR-specific.
Updated•3 months ago
|
![]() |
||
Updated•2 months ago
|
Description
•