Updates:
Status: Fixed
Comment #9 on issue 7429 by mbel...@chromium.org: CPU spin on some pages
http://code.google.com/p/chromium/issues/detail?id=7429
Fix submitted.
http://codereview.chromium.org/21122
The problem is that webkit's timers are all based off the WTF/CurrentTime
implementation, but the bridge was doing math between a webkit that
implementation of currentTime and Chromium's base/Time implementation.
Subtracting two different times leads to skew, which turned out to
always be negative, so the CPU was spinning for most all timers.
This bug was introduced during the merge which brought in timers. From
the outside, functionality was correct (timers fired at the right time),
but internally we could spin the CPU in while waiting for the timer to
fire.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
