Annotate crash reports when no fonts found

NEW
Unassigned

Status

()

Core
Graphics
7 years ago
6 years ago

People

(Reporter: jdm, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
From bug 616426 comment 17:

I think it might make sense to annotate the crashdump if there's a situation
where zero fonts are found.  Seems like we're guessing at the root cause here. 
If the root cause really was no fonts in the directory it would be pretty easy
to figure that out.  Other scenarios are possible here, all the fonts failed to
load, none of the files had extensions '.ttf', yadda, yadda.

I would suggest tracking the data below.  If the total fonts loaded is 0, then
annotate the crashdump with that info:

- whether the $root/system dir was found
- how many files were found
- how many .ttf files were found
- how many fonts failed to load

This way, if the crash still does occur at least we'll have a better idea as to
which scenario is causing the crash.  Kinda sucky that manufacturers can hack
the Skia code to load fonts from random places.

---

Note, this can't happen in the child process until bug 581341 is fixed.
QA Contact: thebes → jdaggett
You need to log in before you can comment on or make changes to this bug.