[Webkit-unassigned] [Bug 193390] New: Why is the result of FontCascadeFonts::glyphDataForSystemFallback() not kept in the cache?
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun Jan 13 18:29:21 PST 2019
https://bugs.webkit.org/show_bug.cgi?id=193390
Bug ID: 193390
Summary: Why is the result of
FontCascadeFonts::glyphDataForSystemFallback() not
kept in the cache?
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Text
Assignee: webkit-unassigned at lists.webkit.org
Reporter: simon.fraser at apple.com
CC: mmaxfield at apple.com
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.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190114/88b1d6ca/attachment.html>
More information about the webkit-unassigned
mailing list