Closed Bug 1506468 Opened 5 years ago Closed 2 years ago

GPU process crash in igd11dxva64.dll | NDXGI::CDevice::NTStatusToHResult

Categories

(Core :: Audio/Video: Playback, defect, P5)

x86_64
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr60 --- affected
firefox65 --- wontfix
firefox66 --- fix-optional
firefox67 --- affected
firefox70 --- affected
firefox71 --- affected
firefox72 --- affected
firefox75 --- affected

People

(Reporter: jseward, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is
report bp-63941318-8402-4acf-9b04-3b5f90181109.
=============================================================

This was reported 4 times in 4 different instances in the Windows
nightly of 20181108220756.  The actual crashing stack below is 
hopeless, but those of other threads might be useful, in particular
that of "Thread 8, Name: VideoParent".

Top 3 frames of crashing thread:

0 igd11dxva64.dll igd11dxva64.dll@0x2a4e4 
1 d3d11.dll NDXGI::CDevice::NTStatusToHResult 
2 d3d11.dll NDXGI::CDevice::EvictCB 

=============================================================
Flags: needinfo?(jyavenard)
igd11dxva64.dll is in the intel drivers (hardware decoders). That it crash in the VideoParent is kind of expected as it would be used in the GPU process only.

I'm not sure this is actionable... We let the GPU process crash and fall back to software decoding after that. This is why we developed the GPU process architecture to start with.
Flags: needinfo?(jyavenard)
Component: DOM: Device Interfaces → Audio/Video: Playback
Priority: -- → P5
Summary: Crash in igd11dxva64.dll | NDXGI::CDevice::NTStatusToHResult → GPU process crash in igd11dxva64.dll | NDXGI::CDevice::NTStatusToHResult

¡Hola!

Got bp-c41686e7-a6ac-4ac2-9343-454760191109 on Build ID 20191108095936

Updating flags per the Crash Data section.

¡Gracias!
Alex

Hardware: Unspecified → x86_64
Version: unspecified → Trunk
See Also: → 1479795
QA Whiteboard: qa-not-actionable

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.