Closed
Bug 1804656
Opened 3 years ago
Closed 2 years ago
Crash in [@ CContext::TID3D11DeviceContext_OMSetRenderTargets_<T>]
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: gsvelto, Unassigned)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/8b8c3ae0-bc14-444d-8ca9-a21290221207
Reason: EXCEPTION_ACCESS_VIOLATION_WRITE
Top 10 frames of crashing thread:
0 d3d11.dll CContext::TID3D11DeviceContext_OMSetRenderTargets_<2>
1 libGLESv2.dll rx::StateManager11::syncFramebuffer gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2029
1 libGLESv2.dll rx::StateManager11::updateState gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp:2274
2 libGLESv2.dll rx::Context11::drawArrays gfx/angle/checkout/src/libANGLE/renderer/d3d/d3d11/Context11.cpp:268
3 libGLESv2.dll gl::Context::drawArrays gfx/angle/checkout/src/libANGLE/Context.inl.h:131
3 libGLESv2.dll GL_DrawArrays gfx/angle/checkout/src/libGLESv2/entry_points_gles_2_0_autogen.cpp:1063
4 xul.dll webrender::device::gl::Device::draw_nonindexed_points gfx/wr/webrender/src/device/gl.rs:3645
5 xul.dll webrender::renderer::gpu_cache::GpuCacheTexture::flush gfx/wr/webrender/src/renderer/gpu_cache.rs:370
5 xul.dll webrender::renderer::Renderer::update_gpu_cache gfx/wr/webrender/src/renderer/gpu_cache.rs:471
6 xul.dll webrender::renderer::Renderer::prepare_gpu_cache gfx/wr/webrender/src/renderer/gpu_cache.rs:497
This is a NULL pointer access happening somewhere within Direct 3D libraries but starting in our code. All the affected machines are based on Ivy Bridge CPUs w/ integrated graphics and use the Intel driver version 10.18.10.4358 or older.
Updated•3 years ago
|
Severity: -- → S3
Component: Graphics → Graphics: WebRender
Comment 1•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.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•