Open
Bug 1892368
Opened 1 month ago
Updated 24 days ago
Crash in [@ <unknown in igd10iumd64.dll> | CContext::TID3D11DeviceContext_SetShader_<T>]
Categories
(Core :: Graphics, defect)
Tracking
()
NEW
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/518a3e25-2476-4bd5-bb42-639650240419
Reason: EXCEPTION_ACCESS_VIOLATION_READ
Top 10 frames of crashing thread:
0 igd10iumd64.dll <unknown in igd10iumd64.dll>
1 d3d11.dll CContext::TID3D11DeviceContext_SetShader_<2, 0>
2 libGLESv2.dll rx::StateManager11::setVertexShader gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2447
2 libGLESv2.dll rx::StateManager11::setDrawShaders gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2435
2 libGLESv2.dll rx::StateManager11::syncProgram gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:3001
2 libGLESv2.dll rx::StateManager11::updateState gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2360
3 libGLESv2.dll rx::Context11::drawElementsImpl gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/Context11.cpp:323
3 libGLESv2.dll rx::Context11::drawElementsInstanced gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/Context11.cpp:365
4 libGLESv2.dll gl::Context::drawElementsInstanced gfx/angle/checkout/src/libANGLE/Context.cpp:2709
5 libGLESv2.dll GL_DrawElementsInstanced gfx/angle/checkout/src/libGLESv2/entry_points_gles_3_0_autogen.cpp:746
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- First crash report: 2024-03-12
- Process type: GPU
- Is startup crash: No
- Has user comments: No
- Is null crash: Yes - 1 out of 11 crashes happened on null or near null memory address
Reporter | ||
Comment 1•1 month 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.
Component: General → Graphics
Updated•24 days ago
|
Severity: -- → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•