1719666 - Crash in [@ <unknown in igd10iumd64.dll> | CPixelShader::CLS::FinalConstruct]

Status: NEW

(Core :: Graphics: Layers, defect)

Description

[Sean Feng [:sefeng]]

Maybe Fission related. (DOMFissionEnabled=1)

Crash report: https://crash-stats.mozilla.org/report/index/1767c069-5714-407b-8ca2-f06f40210707

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0 igd10iumd64.dll <unknown in igd10iumd64.dll> 
1 igd10iumd64.dll <unknown in igd10iumd64.dll> 
2 igd10iumd64.dll <unknown in igd10iumd64.dll> 
3 igd10iumd64.dll <unknown in igd10iumd64.dll> 
4 igd10iumd64.dll <unknown in igd10iumd64.dll> 
5 d3d11.dll void CPixelShader::CLS::FinalConstruct 
6 d3d11.dll void CLayeredObjectWithCLS<class CPixelShader>::FinalConstruct 
7 d3d11.dll static void CLayeredObjectWithCLS<class CPixelShader>::CreateInstance 
8 d3d11.dll long CDevice::CreateLayeredChild 
9 d3d11.dll long NDXGI::CDevice::CreateLayeredChild 

We have many other crashes in igd10iumd64.dll, so this is possibly a dup of them.

Comment 1

[Chris Peterson [:cpeterson]]

This doesn't look like a Fission crash, even though the crash report in comment 0 has DOMFissionEnabled=1.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The bug is linked to a topcrash signature, which matches the following criterion:

• Top 5 GPU process crashes on release

:bhood, could you consider increasing the severity of this top-crash bug?

For more information, please visit auto_nag documentation.

Comment 3

[Bob Hood [:bhood]]

Crash volume appears to be low-to-non-existent in recent releases, so I will leave Severity were Jeff place it.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.

For more information, please visit auto_nag documentation.