Bug 193390 - Why is the result of FontCascadeFonts::glyphDataForSystemFallback() not kept in the cache?
Summary: Why is the result of FontCascadeFonts::glyphDataForSystemFallback() not kept ...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Text (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-13 18:29 PST by Simon Fraser (smfr)
Modified: 2019-01-13 18:31 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Fraser (smfr) 2019-01-13 18:29:21 PST 
When running this subtest of Speedometer2: https://browserbench.org/Speedometer2.0/?suite=BackboneJS-TodoMVC&iterationCount=100
we enter FontCascadeFonts::glyphDataForSystemFallback() multiple times, each time for the same glyph (❯ Heavy Right-Pointing Angle Quotation Mark Ornament).

The caller, FontCascadeFonts::glyphDataForCharacter(), puts the resulting glyph in the cache, but later on we go through glyphDataForSystemFallback() again and I'm not sure why.
Comment 1 Simon Fraser (smfr) 2019-01-13 18:31:23 PST 
We spend 34ms in 34.00 ms in FontCascadeFonts::glyphDataForSystemFallback() during a 15s run.