Comment #16 on issue 22948 by jamesr.gatech: web pages eating lots of CPU http://code.google.com/p/chromium/issues/detail?id=22948
My initial suspicion is that a large number of timers are being set - either a large number of concurrent setInterval()s building up over time or a bunch of setTimeout()s somehow getting enqueued quickly. I'm not sure how to verify this in a running prod browser, but it should be very easy to check in a debug build by putting a breakpoint in ScheduledAction::execute(). The callstack in #7 is what you would typically see for either a setTimeout() or setInterval() call and the callstack in #8 is the postprocessing, most likely blocked in the QueryPerformanceCounter(). -- 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 -~----------~----~----~----~------~----~------~--~---
