Changeset 107794 in webkit


Ignore:
Timestamp:
Feb 15, 2012 1:24:36 AM (12 years ago)
Author:
tonyg@chromium.org
Message:

[chromium] Don't use increased FontCache size on Android
https://bugs.webkit.org/show_bug.cgi?id=78656

Reviewed by Adam Barth.

The chromium port uses a larger font cache size because it increases
performance on the intl1 and intl2 page cyclers. However, on Android
devices where resources are more constrained, it isn't desireable to
allow the FontCache to grow so big.

No new tests because no testable difference in functionality.

  • platform/graphics/FontCache.cpp:

(WebCore):

Location:
trunk/Source/WebCore
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/WebCore/ChangeLog

    r107793 r107794  
     12012-02-15  Tony Gentilcore  <tonyg@chromium.org>
     2
     3        [chromium] Don't use increased FontCache size on Android
     4        https://bugs.webkit.org/show_bug.cgi?id=78656
     5
     6        Reviewed by Adam Barth.
     7
     8        The chromium port uses a larger font cache size because it increases
     9        performance on the intl1 and intl2 page cyclers. However, on Android
     10        devices where resources are more constrained, it isn't desireable to
     11        allow the FontCache to grow so big.
     12
     13        No new tests because no testable difference in functionality.
     14
     15        * platform/graphics/FontCache.cpp:
     16        (WebCore):
     17
    1182012-02-15  Roland Steiner  <rolandsteiner@chromium.org>
    219
  • trunk/Source/WebCore/platform/graphics/FontCache.cpp

    r103243 r107794  
    253253static FontDataCache* gFontDataCache = 0;
    254254
    255 #if PLATFORM(CHROMIUM)
     255#if PLATFORM(CHROMIUM) && !OS(ANDROID)
    256256const int cMaxInactiveFontData = 250;
    257257const int cTargetInactiveFontData = 200;
Note: See TracChangeset for help on using the changeset viewer.