Open
Bug 1871999
Opened 5 months ago
Updated 5 months ago
Crash in [@ igd10iumd64.dll | CContext::TID3D11DeviceContext_OMSetRenderTargets_<T>]
Categories
(Core :: Graphics, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox123 | --- | 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/9df552eb-488c-4457-af0d-5a99b0231223
Reason: EXCEPTION_ACCESS_VIOLATION_WRITE
Top 10 frames of crashing thread:
0 igd10iumd64.dll igd10iumd64.dll@0x1ae32
1 igd10iumd64.dll igd10iumd64.dll@0xe37b6
2 igd10iumd64.dll igd10iumd64.dll@0xe33b9
3 d3d11.dll CContext::TID3D11DeviceContext_OMSetRenderTargets_<2>
4 libGLESv2.dll rx::StateManager11::syncFramebuffer gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2075
4 libGLESv2.dll rx::StateManager11::updateState gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2320
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
6 libGLESv2.dll gl::Context::drawElementsInstanced gfx/angle/checkout/src/libANGLE/Context.cpp:2709
7 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: 2023-10-28
- Process type: GPU
- Is startup crash: No
- Has user comments: No
- Is null crash: Yes - 2 out of 5 crashes happened on null or near null memory address
Reporter | ||
Comment 1•5 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.
Component: General → Graphics
Comment 2•5 months ago
|
||
Rare crash, nothing urgent, and appears to be a crash within d3d, so might be fixed by driver updates anyway.
Severity: -- → S4
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•