[Webkit-unassigned] [Bug 37292] New: http://trac.webkit.org/changeset/57215 caused perf/memory regressions

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Apr 8 14:15:50 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=37292

           Summary: http://trac.webkit.org/changeset/57215 caused
                    perf/memory regressions
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Text
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ojan at chromium.org
                CC: hyatt at apple.com, mitz at webkit.org, fishd at chromium.org,
                    dglazkov at chromium.org, enrica at apple.com


http://trac.webkit.org/changeset/57215 caused a ~6% perf regression on Mac on
Chromium's page cycler intl2 test and a ~3% regression on page cycler intl2.

It caused a 2-8% memory regression on Chromium's intl1, intl2 and moz page
cyclers.

I'm pretty sure Safari would see the same regressions. At the very least,
Chromium uses the same font code as Safari on the Mac.

Chromium will be cutting a release very soon (in a matter of days). Is there
something we can do to address this regression before then? Can we put this
behind a flag until the perf/memory issues are resolved?

-- 
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