Closed Bug 1678367 Opened 5 years ago Closed 4 years ago

Crash in [@ OpenDxva11]

Categories

(Core :: Graphics, defect, P3)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: sefeng211, Unassigned)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/5d744c9b-54c8-4be6-92a9-f742d0201116

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0 igd11dxva64.dll OpenDxva11 
1 igd11dxva64.dll OpenDxva11 
2 igd10iumd64.dll GTPIN_IGC_Instrument 
3 d3d11.dll static void NDXGI::CDevice::TrimNotificationCallback 
4 dxcore.dll DxTrimWnfCallback 
5 ntdll.dll RtlpWnfWalkUserSubscriptionList 
6 ntdll.dll RtlpWnfProcessCurrentDescriptor 
7 ntdll.dll RtlpWnfNotificationThread 
8 ntdll.dll TppExecuteWaitCallback 
9 ntdll.dll TppWorkerThread 

This is not a new nightly crash, however, we have been hit this crash for a while.

The severity field is not set for this bug.
:gcp, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(gpascutto)

Going to redirect to graphics as this appears to be an Intel video driver crash.

Component: Other → Graphics
Flags: needinfo?(gpascutto)
Product: External Software Affecting Firefox → Core
Severity: -- → S3
Priority: -- → P3

https://support.mozilla.org/en-US/questions/1329284#answer-1405539 reports crashes on Windows 10 running high contrast mode with similar stack and graphics (Intel HD Graphics 620) to the crash report in comment 0. Even the same driver version igd10iumd64.dll 23.20.16.4973

Apparently the problems started with version 73 - related to Bug 1539212 - implement readability backplate for high contrast mode - per https://support.mozilla.org/en-US/questions/1281791 https://www.mozilla.org/en-US/firefox/73.0/releasenotes/

bp-3198c6aa-97f3-452d-8e04-89a760210413 <unknown in igd10iumd64.dll> | CContext::TID3D11DeviceContext_OMSetBlendState_<T>
bp-9021e901-e67a-4554-a8d3-94ded0210413 @0x0 | <unknown in igd11dxva64.dll> | CVideoProcessor::CLS::FinalConstruct
the more common signatures ...
bp-c0ee6a85-9fcd-454c-a24d-b53320210413 <unknown in igd10iumd64.dll> | CContext::TID3D11DeviceContext_ClearView_<T>
bp-ddbc7e62-c363-4139-ae40-c9e2a0210413 <unknown in igd11dxva64.dll> | <unknown in igd10iumd64.dll> | NDXGI::CDevice::TrimNotificationCallback
bp-def10b7c-bd41-45e9-8ccb-f32200210413 <unknown in igd10iumd64.dll> | CContext::UMQueryOM_DepthState_

crash rate is at zero

Flags: needinfo?(sefeng)

Yeah....Do we know what fixed it?

Flags: needinfo?(sefeng)

(In reply to Sean Feng [:sefeng] from comment #5)

Yeah....Do we know what fixed it?

My guess would be some sort of change to the signature. although a search for anything with 'OpenDxva11' in it doesn't show up. Hard to say.

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