Crash in [@ igd10iumd64.dll | rx::ShaderConstants11::updateBuffer]
Categories
(Core :: Graphics: WebRender, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox127 | --- | affected |
People
(Reporter: release-mgmt-account-bot, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/77208f30-eab8-404b-a2a3-bdc990240507
Reason: EXCEPTION_ACCESS_VIOLATION_WRITE
Top 10 frames of crashing thread:
0 igd10iumd64.dll igd10iumd64.dll@0x1b2ee5
1 libGLESv2.dll rx::ShaderConstants11::updateBuffer gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:681
2 d3d11.dll CDevice::CondObjectLock::CondObjectLock
3 d3d11.dll CContext::TID3D11DeviceContext_IASetVertexBuffers_<2>
4 libGLESv2.dll rx::StateManager11::applyVertexBufferChanges gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2193
4 libGLESv2.dll rx::StateManager11::applyVertexBuffers gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:3223
4 libGLESv2.dll rx::StateManager11::syncVertexBuffersAndInputLayout gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:3073
4 libGLESv2.dll rx::StateManager11::updateState gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2369
5 libGLESv2.dll rx::Context11::drawElementsImpl gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/Context11.cpp:323
5 libGLESv2.dll rx::Context11::drawElementsInstanced gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/Context11.cpp:365
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- First crash report: 2024-03-08
- Process type: GPU
- Is startup crash: No
- Has user comments: No
- Is null crash: No
Reporter | ||
Comment 1•8 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•8 months ago
|
||
Sotaro, seems like some sort of shutdown/device lost issue maybe? Ideas?
Reporter | ||
Comment 4•8 months ago
|
||
Copying crash signatures from duplicate bugs.
Comment 5•7 months ago
|
||
It is not clear why the crashes happened. But the crashes seemed to happen by driver problems. Driver date of ShaderConstants11::updateBuffer crashes were 2015/2016. Driver date of TID3D11DeviceContext_OMSetDepthStencilState_ crashes were 2017.
Description
•