Closed
Bug 1658207
Opened 4 years ago
Closed 4 years ago
[shared fontlist] Family character-map is not always set/used properly to accelerate fallback searches
Categories
(Core :: Layout: Text and Fonts, defect)
Core
Layout: Text and Fonts
Tracking
()
RESOLVED
FIXED
81 Branch
Tracking | Status | |
---|---|---|
firefox81 | --- | fixed |
People
(Reporter: jfkthame, Assigned: jfkthame)
References
Details
Attachments
(1 file)
Doing some profiling of text-intensive actions, I realized that we don't always use the character map in fontlist::Family records correctly to optimize fallback searches, and we don't always set it up when we should as a result of the InitializeFamily message.
(Noticed while profiling pinch-zoom operations in bug 1657440 (edit: actually bug 1656156); the profile showed more time in SearchAllFontsForChar and InitializeFamily than I would have expected. With this fixed, those methods no longer appear as "hotspots" in the profile.)
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Assignee: nobody → jfkthame
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•4 years ago
|
||
In my local opt (but non-pgo) build, this accelerates reflows when zooming wikipedia.org (which is quite font-fallback-heavy, because of the mix of languages) by at least 20%.
Pushed by jkew@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/16346122a824
Set up and use the mCharacterMap in shared Family records more correctly, to accelerate font fallback searches. r=jwatt
Comment 4•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox81:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•