1516446 - Crash in vcruntime140.dll@0xc4f8 | gfxDWriteFontEntry::CopyFontTable

Status: RESOLVED WORKSFORME

(Core :: Graphics: Text, defect, P3)

Description

[Liz Henry (:lizzard) (privacy/fingerprinting team)]

This bug was filed from the Socorro interface and is
report bp-37b060e6-4a5d-40c6-89d9-80b630181226.
=============================================================

342 crashes on Nightly in the last week from 10 installations. 


Top 10 frames of crashing thread:

0 vcruntime140.dll vcruntime140.dll@0xc4f8 
1 xul.dll gfxDWriteFontEntry::CopyFontTable gfx/thebes/gfxDWriteFontList.cpp:424
2 xul.dll gfxFontEntry::GetFontTable gfx/thebes/gfxFontEntry.cpp:542
3 xul.dll gfxDWriteFontEntry::ReadCMAP gfx/thebes/gfxDWriteFontList.cpp:503
4 xul.dll gfxFontEntry::TestCharacterMap gfx/thebes/gfxFontEntry.cpp:151
5 xul.dll gfxFontGroup::FindFontForChar gfx/thebes/gfxTextRun.cpp:2861
6 xul.dll static void gfxFontGroup::InitScriptRun<char16_t> gfx/thebes/gfxTextRun.cpp:2409
7 xul.dll gfxFontGroup::InitTextRun<char16_t> gfx/thebes/gfxTextRun.cpp:2331
8 xul.dll gfxFontGroup::MakeTextRun gfx/thebes/gfxTextRun.cpp:2206
9 xul.dll void BuildTextRunsScanner::FlushFrames layout/generic/nsTextFrame.cpp:1658

=============================================================

Comment 1

[Lee Salzman [:lsalzman]]

Jonathan, the recent spike in crashes from this seems weird. I'm not sure if this is a regression. It doesn't look like we landed any changes around that time that might aggravate this, as far as I can guess. I wonder if some font in the wild just got disseminated that is causing this?

Comment 2

[Jonathan Kew [:jfkthame]]

It looks to me like these reports -- or at least the dozen or so that I sampled, from several different install times -- are all coming from the same system/user. I think someone was experiencing this crash on Fx64; then they've tried installing a number of Nightly builds, and the same crash is persisting on all those as well.

Given the crash reason "EXCEPTION_IN_PAGE_ERROR_READ / STATUS_DEVICE_DATA_ERROR", I wonder if they've got a particular font file that can't be read, maybe because of a disk error or similar fault, and every time they try to launch Firefox, we try to access that font. Or maybe it's a bad font file that trips over a bug within DirectWrite when it tries to read it.

It's not clear to me there's anything we can do here; I suspect a single bad machine (or damaged OS installation?). Given they're running Win7, it could be old hardware, maybe with a dying disk or something.

Comment 3

[Marcia Knous [:marcia]]

Crashes stopped in the 12/30 build. As noted in Comment 2 it looks as if all the crashes are from a single install.

Comment 4

[Marcia Knous [:marcia]]

Resolving this as WFM. No further crashes, single install and based on crash reason likely not much we can do about it.