Open Bug 1356399 Opened 5 years ago Updated 9 months ago

Crash in TrueTypeFontMetricsBuilder::GetBlackBox

Categories

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

All
Windows
defect

Tracking

()

Tracking Status
firefox-esr78 --- affected
firefox-esr91 --- affected
firefox92 --- affected
firefox93 --- affected
firefox94 --- affected

People

(Reporter: mccr8, Unassigned)

References

Details

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

Crash Data

This bug was filed from the Socorro interface and is 
report bp-ea346fd8-0b68-4ac5-bff3-0dc082170413.
=============================================================

This is the #3 top crash on Aurora for 4/13 build. There are 492 crashes on Aurora with this signature in the last week, across 10 installations, so presumably there's something terrible wrong with a few people's computers. I'm not sure if we can do anything about this, but I figured we should have a bug on file for such a common crash.
Jonathan, any ideas about what we might be able to do here?
Flags: needinfo?(jfkthame)
Not really, unless we can reproduce it, or get a user who is experiencing it to do some investigation -- e.g. disabling fonts until the problem stops happening, to isolate the font involved. (It looks like an internal DirectWrite crash that I'm guessing is specific to a certain font/version that has something anomalous about it....)
Flags: needinfo?(jfkthame)
Whiteboard: [gfx-noted]
(In reply to Jonathan Kew (:jfkthame) from comment #2)
> Not really, unless we can reproduce it, or get a user who is experiencing it
> to do some investigation -- e.g. disabling fonts until the problem stops
> happening, to isolate the font involved. (It looks like an internal
> DirectWrite crash that I'm guessing is specific to a certain font/version
> that has something anomalous about it....)

In Windows 7, does hiding a font suffice.  If not, is there an alternative process to avoid deleting?  (My win7 has 277 fonts)
Just FYI, these (remaining) crashes are all EXCEPTION_IN_PAGE_ERROR_READ with various disk errors. What is happening is that the font file is mmap'd and as Windows API touches pages in the buffer, the user's computers is reporting disk errors and the process is killed. https://bugzilla.mozilla.org/show_bug.cgi?id=771138#c4 gives some thoughts on these sort of issues that we hit in a few places of browser.

Five years later and we're still seeing 20–50 reports of this crash per day.

The crash reasons still all look like disk errors reported deep inside dwrite.dll:

EXCEPTION_IN_PAGE_ERROR_READ / STATUS_BAD_COMPRESSION_BUFFER
EXCEPTION_IN_PAGE_ERROR_READ / STATUS_DEVICE_DATA_ERROR
EXCEPTION_IN_PAGE_ERROR_READ / STATUS_IO_DEVICE_ERROR
EXCEPTION_IN_PAGE_ERROR_READ / STATUS_IO_TIMEOUT
EXCEPTION_IN_PAGE_ERROR_READ / STATUS_NO_SUCH_DEVICE
EXCEPTION_IN_PAGE_ERROR_READ / STATUS_UNEXPECTED_NETWORK_ERROR
EXCEPTION_IN_PAGE_ERROR_READ / STATUS_VOLUME_DISMOUNTED

OS: Windows 7 → Windows
Hardware: x86 → All
You need to log in before you can comment on or make changes to this bug.