[Webkit-unassigned] [Bug 95866] Refactor WebCore::FontData handling to clarify pointer ownership

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Sep 6 11:04:49 PDT 2012


--- Comment #5 from Stephen Chenney <schenney at chromium.org>  2012-09-06 11:05:03 PST ---
Some FontData is owned by SimpleFontData, but that is all correctly accounted for so we can ignore it for the purposes of this discussion.

All other FontData is requested via FontFallbackList::getFontData:
  FontFallbackList::getFontData calls
    FontCache::getFontData calls
      CSSFontSelector::getFontData calls
        CSSFontFace::getFontData calls
          CSSFontFaceSelector::getFontData which allocates FontData
        CSSSegmentedFontFace::getFontData which allocates FontData

On the return path, FontCache caches and owns non-custom FontData, while FontFallbackList owns custom FontData. There is no way, as far as I can tell, to get a custom FontData object without going through FontFallbackList and FontFallbackList always caches that custom font for removal when no longer used.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list