Closed Bug 1652405 Opened 4 years ago Closed 4 years ago

Crash in [@ NtGdiDdDDICreateContextVirtual]

Categories

(Core :: Graphics, defect, P3)

x86
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox81 --- affected

People

(Reporter: gsvelto, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-e46709df-4f52-4fe0-985e-037b40200712.

Top 10 frames of crashing thread:

0 win32u.dll NtGdiDdDDICreateContextVirtual 
1 d3d11.dll long __stdcall CallAndLogImpl<long  
2 d3d11.dll long __thiscall NDXGI::CDevice::CreateContextVirtual2 
3 d3d11.dll static long __stdcall NDXGI::CDevice::CreateContextVirtualCB 
4 nvwgf2um_cfg.dll nvwgf2um_cfg.dll@0x128dc8 
5 nvwgf2um_cfg.dll nvwgf2um_cfg.dll@0xc60c81 
6 nvwgf2um_cfg.dll nvwgf2um_cfg.dll@0x59a7d 
7 nvwgf2um_cfg.dll nvwgf2um_cfg.dll@0x5a36e 
8 nvwgf2um_cfg.dll nvwgf2um_cfg.dll@0x5af09 
9 nvwgf2um_cfg.dll nvwgf2um_cfg.dll@0x522c0 

This is a 32-bit only crash that happens exclusively with nVidia's graphics driver version 27.21.14.5541 which should correspond with version 451.48 of nVidia's driver bundle. This is a fairly recent version but not the latest one (that would be 451.67). Filing this in case the volume increases and we might want to block this version.

Alenio, just flagging this for you because we are seeing some crashes come in associated with a specific driver version. Any suggestions for a workaround?

Flags: needinfo?(aleino)
Severity: -- → S3
Priority: -- → P3

Thanks for reporting. I'll try to have a look soon, but since this is an 32-bit only issue I don't think I can give it top priority.

I'm not very familiar with Mozilla crash reports yet.
A few questions:
Does anything from the crash report stand out to you?
Is it possible to dig up the URL that's crashing?
Any high level picture of whats going on? (Did the user just arrive at a page, or did they perform some other action at the time of the crash?)

Flags: needinfo?(aleino) → needinfo?(gsvelto)

The uncaught exception that's triggering the crash is an EXCEPTION_INVALID_HANDLE, so given these functions work initialize a D3D device maybe a wrong value was being passed in? The stack shows our code entering Windows code at D3D11CreateDeviceImpl(), then we get all the way down to NDXGI::CDevice::CreateDriverInstance(). At that point we enter the nVidia driver code which we exit at NDXGI::CDevice::CreateContextVirtualCB(). I might get a better stack trace if I pull nVidia symbol files which I was planning to do soon.

Flags: needinfo?(gsvelto)
Depends on: 1655476

Closing because no crashes reported for 12 weeks.

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.