Closed
Bug 1653577
Opened 5 years ago
Closed 5 years ago
Add some NS_ASSERTIONs for unexpected failures in directwrite font code
Categories
(Core :: Graphics: Text, enhancement)
Tracking
()
RESOLVED
FIXED
mozilla80
Tracking | Status | |
---|---|---|
firefox80 | --- | fixed |
People
(Reporter: jfkthame, Assigned: jfkthame)
Details
Attachments
(1 file)
There are several places in gfxDWriteFontList::MakePlatformFont
, the method that instantiates a platform font reference from downloaded webfont data, that could in theory fail, and we just silently return.
To help diagnose any case where we're actually encountering such failures (which could account for reftest flakiness on Win7, for example, if directwrite sometimes fails to accept the downloaded font), I'd like to add (non-fatal) NS_ASSERTION messages so that logs will clearly show where things went wrong.
(I have no firm evidence that we're ever actually experiencing any of these failure cases in the CI test suites, in which case the assertions will simply never fire; but if it does happen we really ought to know about it.)
Assignee | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Assignee: nobody → jfkthame
Status: NEW → ASSIGNED
Pushed by jkew@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3030fc89d01e
Add NS_ASSERTION to various failure cases in gfxDWriteFontList::MakePlatformFont, rather than just silently failing. r=lsalzman
Comment 3•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox80:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in
before you can comment on or make changes to this bug.
Description
•