Crash in [@ mozilla::wr::SpaceAndClipChainHelper::SpaceAndClipChainHelper]
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: office, Unassigned)
Details
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/40d8365f-daa6-4809-8f69-c660e0221111
Reason: EXCEPTION_ACCESS_VIOLATION_WRITE
Top 10 frames of crashing thread:
0 xul.dll mozilla::wr::SpaceAndClipChainHelper::SpaceAndClipChainHelper gfx/webrender_bindings/WebRenderAPI.h:800
0 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList gfx/layers/wr/WebRenderCommandBuilder.cpp:2065
1 xul.dll mozilla::nsDisplayTransform::CreateWebRenderCommands layout/painting/nsDisplayList.cpp:6700
2 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommands gfx/layers/wr/WebRenderCommandBuilder.cpp:1822
2 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList gfx/layers/wr/WebRenderCommandBuilder.cpp:2085
3 xul.dll mozilla::nsDisplayTransform::CreateWebRenderCommands layout/painting/nsDisplayList.cpp:6700
4 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommands gfx/layers/wr/WebRenderCommandBuilder.cpp:1822
4 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList gfx/layers/wr/WebRenderCommandBuilder.cpp:2085
5 xul.dll mozilla::nsDisplayWrapList::CreateWebRenderCommandsNewClipListOption layout/painting/nsDisplayList.cpp:4632
5 xul.dll mozilla::nsDisplayWrapList::CreateWebRenderCommands layout/painting/nsDisplayList.h:4975
While reading https://www.heute.at/s/wiener-von-mitschueler-verpruegelt-augenhoehle-gebrochen-100237811
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•3 years ago
|
||
The bug has a crash signature, thus the bug will be considered confirmed.
Comment 3•3 years ago
|
||
There are all on family 23 model 113 stepping 0 cpus but they all seem to have a different gpu, so unlikely to be from one machine.
Comment 4•3 years ago
|
||
This crash likely came from a different signature that changed when we added inline call stacks. The volume seems low and this is a very hot code path so this seems unlikely to be very actionable.
Updated•3 years ago
|
Comment 5•2 years ago
|
||
I stumbled upon this because PHC caught a crash that appears like a buffer overflow but I don't think it is a real one. All crashes under this signature are still coming from family 23 model 113 stepping 0 but from different users. Chances are we're hitting a CPU bug even though it is peculiar that the failure remained the same across several Firefox versions.
Comment 6•2 years ago
|
||
Given the volume and lack of repro steps, there is nothing we can do about this. Closing for now, but please reopen if volume or relevant information changes.
Description
•