Crash report: https://crash-stats.mozilla.org/report/index/39eaf244-cfae-418d-8343-c66fb0211028

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 mozglue_static::oom_hook::hook mozglue/static/rust/lib.rs:115
3 xul.dll std::alloc::rust_oom ../c8dfcfe046a7680554bf4eb612bad840e7631c4b//library/std/src/alloc.rs:329
4 xul.dll alloc::alloc::__alloc_error_handler::__rg_oom ../c8dfcfe046a7680554bf4eb612bad840e7631c4b//library/alloc/src/alloc.rs:398
5 xul.dll __rust_alloc_error_handler 
6 xul.dll webrender::renderer::Renderer::render_impl gfx/wr/webrender/src/renderer/mod.rs:1960
7 xul.dll webrender::renderer::Renderer::render gfx/wr/webrender/src/renderer/mod.rs:1723
8 xul.dll webrender_bindings::bindings::wr_renderer_render gfx/webrender_bindings/src/bindings.rs:622
9 xul.dll mozilla::wr::RenderThread::UpdateAndRender gfx/webrender_bindings/RenderThread.cpp:501

OOM size of around 1MB.

This was topcrash #3 for 95.0b9 and has 60-180 affected installations per beta release.

Removed callstack, pasted in incorrect bug.

A lot of the crashes are on buggy AMD CPUs: https://crash-stats.mozilla.org/report/index/a4a285a4-43a8-4f4e-ab4b-82a920211202

Overall crash rates are constant in 95 beta. Stalled, we're not sure what the cause is. Maybe be related to a buggy amd cpu.

This WebRender OOM spiked in Firefox 99.

(In reply to Chris Peterson [:cpeterson] from comment #5)

This WebRender OOM spiked in Firefox 99.

Roughly double - at a rate that exists through today.

Still a lot on AMD not much on Nightly

https://crash-stats.mozilla.org/report/index/52d42d02-0b69-4c1f-8ea4-36f5c0230310

The crash volume here suggests that we may have successfully mitigated this crash in Release a while ago, and only ESR would now be largely impacted by this. Do we have any idea what may have caused this? Any potential uplift?

I can't think of anything we've landed recently that would have fixed this. However, being an OOM, it might be that it's no longer occurring due to memory related optimizations of fixes outside of WR itself.