[Webkit-unassigned] [Bug 30833] New: Chromium builds should not use JavaScriptCore/wtf/CurrentTime.cpp

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 27 13:55:56 PDT 2009


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

           Summary: Chromium builds should not use
                    JavaScriptCore/wtf/CurrentTime.cpp
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jamesr at chromium.org


Chromium uses a different method to calculate the current time than is used in
JavaScriptCore/wtf/CurrentTime.cpp. This can lead to time skew when calls to
currentTime() and Chromium's time function are mixed.  In particular, timers
can get scheduled in the past which leads to 100% CPU use. See
http://code.google.com/p/chromium/issues/detail?id=25892 for an example.

Chromium provides its own implementation of WTF::currentTime() which it should
always use instead.

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