This bug is for crash report bp-003bc36c-259b-437e-a1f5-f53ed0200806.

Top 10 frames of crashing thread:

0 xul.dll PLDHashTable::PLDHashTable xpcom/ds/PLDHashTable.cpp:194
1 xul.dll mozilla::layers::WebRenderGroupData::WebRenderGroupData gfx/layers/wr/WebRenderCommandBuilder.cpp:2657
2 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateOrRecycleWebRenderUserData<mozilla::layers::WebRenderGroupData> gfx/layers/wr/WebRenderCommandBuilder.h:141
3 xul.dll mozilla::layers::WebRenderCommandBuilder::DoGroupingForDisplayList gfx/layers/wr/WebRenderCommandBuilder.cpp:1409
4 xul.dll nsDisplaySVGWrapper::CreateWebRenderCommands layout/painting/nsDisplayList.cpp:9895
5 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommands gfx/layers/wr/WebRenderCommandBuilder.cpp:1652
6 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList gfx/layers/wr/WebRenderCommandBuilder.cpp:1757
7 xul.dll nsDisplayTransform::CreateWebRenderCommands layout/painting/nsDisplayList.cpp:8019
8 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommands gfx/layers/wr/WebRenderCommandBuilder.cpp:1652
9 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList gfx/layers/wr/WebRenderCommandBuilder.cpp:1757

There are only a 4 crashes from a single installation, but the crash reason is weird. It is crashing on some PLDHashtable internal check, giving the error "Entry size is too large".

As far as I can see, the hash table here is nsTHashtable<nsRefPtrHashKey<WebRenderUserData>>, so I don't understand why we'd be hitting that, unless there's some kind of memory corruption.

MOZ_CRASH Reason (Sanitized) MOZ_CRASH(Entry size is too large)

Bug 1656711 was a recent WebRender/SVG change that landed two days before the first crash and has been backed out.

(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #1)

MOZ_CRASH Reason (Sanitized) MOZ_CRASH(Entry size is too large)

Bug 1656711 was a recent WebRender/SVG change that landed two days before the first crash and has been backed out.

It was backed out because investigating the crash is hard and time consuming, whereas if the crash happens in a build without that patch then we know its not to blame and took virtually no time to figure that out.

Closing because no crashes reported for 12 weeks.