We can spend lots of time resolving fonts for wikipedia.org on FireTV/GeckView
Categories
(Core :: Graphics: Text, defect)
Tracking
()
People
(Reporter: jesup, Assigned: jfkthame)
References
()
Details
(Keywords: perf, perf:pageload, Whiteboard: [gv][geckoview:fenix:m4])
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
With a FireTV/GeckoView build, font searching/loading can take a lot of time, including a lot of time apparently in read().
Here's a profile with markers from Markus on font searching:
Reporter | ||
Comment 1•6 years ago
|
||
Markus noted that one of the glyphs we fail to find.
Assignee | ||
Comment 2•6 years ago
|
||
Looks like gfxAndroidPlatform::GetCommonFallbackFonts is missing the Noto versions of some language-specific fonts, where it lists only Droid Sans versions; in particular, adding Noto Sans Armenian ought to help this profile.
Assignee | ||
Comment 3•6 years ago
|
||
Reporter | ||
Updated•6 years ago
|
Assignee | ||
Comment 4•6 years ago
|
||
Note that while the patch here should help with cases like the Armenian that shows up in this profile, it'll still be possible to hit the "worst-case" behavior if the page has characters that are not actually supported by any installed font.
So this issue isn't really resolved by this patch, it's just an attempt to eliminate some of the cases where it happens. It's highly dependent on what characters are present in the page.
Updated•6 years ago
|
Comment 6•6 years ago
|
||
bugherder |
Comment 7•6 years ago
|
||
Jonathan, can you please uplift this Noto font fix to 67 Beta when you return from PTO? Fenix 1.0 will ship GeckoView 67. Wikipedia is a popular mobile site, so it would be good fix this in Fenix 1.0.
Assignee | ||
Comment 8•6 years ago
|
||
Comment on attachment 9052451 [details]
Bug 1537587 - Add Noto fonts for more languages to Android version of GetCommonFallbackFonts. r?lsalzman
Beta/Release Uplift Approval Request
- Feature/Bug causing the regression: n/a
- User impact if declined: Poor font fallback performance for some scripts on modern Android devices that ship Noto fonts
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Trivial patch just adds some font names to known fallbacks.
- String changes made/needed: n/a
Assignee | ||
Comment 9•6 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #7)
Jonathan, can you please uplift this Noto font fix to 67 Beta when you return from PTO? Fenix 1.0 will ship GeckoView 67. Wikipedia is a popular mobile site, so it would be good fix this in Fenix 1.0.
Sure; there's no reason not to do this, it's a trivial fix. Note that we can still hit the worst-case code path where we search all installed fonts; it depends exactly what's present in the content of the page. This improves things for a number of scripts but isn't a universal fix.
Comment 10•6 years ago
|
||
Comment on attachment 9052451 [details]
Bug 1537587 - Add Noto fonts for more languages to Android version of GetCommonFallbackFonts. r?lsalzman
Perf impact for Geckoview which ships in 67, low risk patch on Nightly for a week, uplift approved for our next 67 beta, thanks.
Comment 11•6 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Updated•3 years ago
|
Description
•