1244512 - crash in gfxDWriteFontEntry::CreateFontFace

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect)

Description

[Zac Campbell]

This bug was filed from the Socorro interface and is 
report bp-96e3f62e-32d0-4e54-990a-e8cd42160122.
=============================================================

Split out from https://bugzilla.mozilla.org/show_bug.cgi?id=1240241

This bug was hit while running fullscreen youtube and alt-tab switching between windows:

Just before that crash occurred I captured this graphics information from about:support

Graphics
--------

Adapter Description: Intel(R) HD Graphics
Adapter Drivers: igdumdim32 igd10iumd32 igd10iumd32
Adapter RAM: Unknown
Asynchronous Pan/Zoom: none
Device ID: 0x0f31
DirectWrite Enabled: false (6.3.9600.18123)
Driver Date: 6-9-2014
Driver Version: 10.18.10.3643
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 221b17aa
Supports Hardware H264 Decoding: No; CheckDeviceFormatConversion failed with error 8876086A
Vendor ID: 0x8086
windowLayerManagerRemote: true
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0
(#0) Assert: [D3D11] 2 CreateTexture2D failure Size(1920,1036) Code: 0x887a0005
(#194) Assert: Failed 2 buffer db=00000000 dw=00000000 for 0, 0, 942, 1134
(#195) Assert: Failed 2 buffer db=00000000 dw=00000000 for 0, 0, 942, 1134
(#196) Assert: Failed 2 buffer db=00000000 dw=00000000 for 0, 0, 942, 1134
(#197) Assert: Failed 2 buffer db=00000000 dw=00000000 for 0, 0, 942, 1134
(#198) Assert: Failed 2 buffer db=00000000 dw=00000000 for 0, 0, 942, 1134




I am not sure if these are the same bug but they are definitely all associated with poor graphics/usability.


During normal use, the Graphics section in about:support reads:

Graphics
--------

Adapter Description: Intel(R) HD Graphics
Adapter Drivers: igdumdim32 igd10iumd32 igd10iumd32
Adapter RAM: Unknown
Asynchronous Pan/Zoom: none
Device ID: 0x0f31
Direct2D Enabled: true
DirectWrite Enabled: true (6.3.9600.18123)
Driver Date: 6-9-2014
Driver Version: 10.18.10.3643
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 221b17aa
Supports Hardware H264 Decoding: Yes
Vendor ID: 0x8086
WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote: true
AzureCanvasBackend: direct2d 1.1
AzureContentBackend: direct2d 1.1
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0

Comment 1

[Loic]

You should update the drivers for your Intel(R) HD Graphics card, they are too old.

Comment 2

[Zac Campbell]

Loic, unfortunately I am not being offered any new drivers for this computer via Windows Update, which is where the average user will get it from.

I can seek out some drivers from the manufacturer but I also don't want to lose the chance to replicate this bug for mstange.

Comment 3

[Jeff Muizelaar [:jrmuizel]]

How reliably can you reproduce this problem?

Comment 4

[Zac Campbell]

Not easily, unfortunately. It took a couple of hours of use to replicate it.

Comment 5

[Markus Stange [:mstange]]

Jonathan, any ideas how this could have happened? Is the DWriteFactory null? Would we even have entered this code in that case?

Comment 6

[Jonathan Kew [:jfkthame]]

No ideas, sorry. If we had failed to initialize the factory in gfxWindowsPlatform::InitDWriteSupport(), then we'd have created a gfxGDIFontList instead of gfxDWriteFontList in gfxWindowsPlatform::CreatePlatformFontList(), and we wouldn't be using the gfxDWriteFont and gfxDWriteFontEntry classes at all; we'd be using the GDI versions.

So if the factory were null, we shouldn't be here, AFAICS.

Comment 7

[Jeff Muizelaar [:jrmuizel]]

This is happening after a device reset.

Comment 8

[Zac Campbell]

https://crash-stats.mozilla.com/report/index/1f8b1af8-afd1-4067-9083-55cb22160322

This time the STR were the same as the original bug 1240241 but on the 44 branch.

I'm going to switch back to Nightly for a while and see if bug 1240241's resolution has resolved this bug too.

Comment 9

[Milan Sreckovic [:milan] (needinfo for best results)]

There seems to have been a device reset, and given that this is in the DWrite/font code, I wouldn't be surprised if bug 1260770 (uplifted to 46) actually takes care of it.

Comment 10

[Robert Kaiser]

(In reply to Milan Sreckovic [:milan] from comment #9)
> There seems to have been a device reset, and given that this is in the
> DWrite/font code, I wouldn't be surprised if bug 1260770 (uplifted to 46)
> actually takes care of it.

And indeed it looks like this has gone away in 46.0b11 \o/

Comment 11

[Zac Campbell]

As this should be in release now, I plan to verify that this has been resolved (as per comment #10) next week and attempt to close the bug. Apologies for the delay.

Comment 12

[u279076]

The volume of this crash has gone down significantly, from 298/day at the peak in April to 36/day in July. All of the recent reports are in Firefox 46 and earlier. Since this no longer shows up in a current Release build I am closing this bug report. 

Zac, feel free to verify this is fixed for you and reopen if not.