Closed Bug 1154271 Opened 10 years ago Closed 9 years ago

crash in nvwgf2um.dll@0x7fec13

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox40 --- affected

People

(Reporter: adalucinet, Unassigned)

Details

(Keywords: crash, Whiteboard: [gfx-noted])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-b4d8a59f-baa3-48a9-b377-506e52150414.
=============================================================

Str:
1. Launch any RTL build (Eg: ar build)
2. Start a Hello conversation and share a tab/window.

Adding ni flag based on bug 1137614 comment 39.

Graphics
Adapter Description	NVIDIA GeForce 210
Adapter Drivers	nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM	1024
Asynchronous Pan/Zoom	none
Device ID	0x0a65
Direct2D Enabled	true
DirectWrite Enabled	true (6.2.9200.16492)
Driver Date	2-3-2015
Driver Version	9.18.13.4144
GPU #2 Active	false
GPU Accelerated Windows	1/1 Direct3D 11 (OMTC)
Subsys ID	040110b0
Vendor ID	0x10de
WebGL Renderer	Google Inc. -- ANGLE (NVIDIA GeForce 210 Direct3D11 vs_4_1 ps_4_1)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d 1.1
AzureContentBackend	direct2d 1.1
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0
This has similar signature to Bug 1154703.
Whiteboard: [gfx-noted]
(In reply to Dan Glastonbury :djg :kamidphish from comment #1)
> This has similar signature to Bug 1154703.

I mean Bug 1154771.
How so? I don't even see similarities in the stacks, other than being in GFX and being a crash in the graphics driver. Otherwise they seem all different to me, and this is NVidia while the other is Intel.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #3)
> How so? I don't even see similarities in the stacks, other than being in GFX
> and being a crash in the graphics driver. Otherwise they seem all different
> to me, and this is NVidia while the other is Intel.

It's been a while since I looked at it, but looking through the stack frames there was some similarity in the code path through d3d11 to the crash.
Mass resolving WFM: signature(s) hasn't(/haven't) reported in past 28 days.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.