Crash in [@ SetEvent | <unknown in igd10iumd64.dll> | CGeometryShader::CLS::FinalConstruct]
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: RyanVM, Unassigned, NeedInfo)
References
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/5a9bf4e0-14a6-4bdc-9232-5766d0231017
Reason: EXCEPTION_INVALID_HANDLE
Top 10 frames of crashing thread:
0 ntdll.dll KiRaiseUserExceptionDispatcher
1 KERNELBASE.dll SetEvent
2 igd10iumd64.dll <unknown in igd10iumd64.dll>
3 d3d11.dll CGeometryShader::CLS::FinalConstruct
4 d3d11.dll CLayeredObjectWithCLS<CGeometryShader>::FinalConstruct
5 d3d11.dll CLayeredObjectWithCLS<CGeometryShader>::CreateInstance
6 d3d11.dll CDevice::CreateLayeredChild
7 d3d11.dll NDXGI::CDevice::CreateLayeredChild
8 d3d11.dll NOutermost::CDevice::CreateLayeredChild
9 d3d11.dll CDevice::CreateAndRecreateLayeredChild<SD3D11LayeredGeometryShaderCreationArgs>
Updated•2 years ago
|
Comment 1•2 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 desktop browser crashes on nightly
For more information, please visit BugBot documentation.
Comment 2•2 years ago
|
||
It would probably be good for someone to set a breakpoint on getGeometryExecutableForPrimitiveType to see if we're triggering geometry shader compilation.
Comment 3•2 years ago
|
||
All of the crashes are on a single driver version: 24.20.100.6194
Updated•2 years ago
|
Comment 4•2 years ago
|
||
I have confirmed on a local windows machine that my build reaches [1] but never reaches [2] which is where the reported crash occurs. This is on a machine with an AMD GPU. Perhaps ANGLE enables a specific workaround on the reporter's hardware / driver that causes us to hit that path?
Comment 5•2 years ago
|
||
gw will send ahale a build that asserts (or something) when the geometry shader is compiled, to check if it tries to on ahale's intel gpu machine. (ignoring driver version for now)
Comment 6•2 years ago
|
||
Ashley will attempt to repro on an Intel GPU with the steps in comment 4. I added an OutputDebugStringA call at each of the locations in [1] and [2] above. Then I verified with DebugView (https://learn.microsoft.com/en-us/sysinternals/downloads/debugview) that I was seeing calls to [1] which always early exited before reaching [2].
Updated•2 years ago
|
Updated•2 years ago
|
Comment 7•2 years ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Comment 8•1 month ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•