[Webkit-unassigned] [Bug 26641] Safari consumes 100% CPU after leaving GMail open (gmail is installing a billion timers)

[bugzilla-daemon at webkit.org]

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


Iain Merrick <husky at google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |husky at google.com




--- Comment #10 from Iain Merrick <husky at google.com>  2011-06-24 07:51:32 PST ---
Any progress on this?

I'm seeing the same thing happening on techcrunch.com on low-end hardware. The site installs thousands of timers and sometimes the browser just can't keep up.

It looks like the minimum timer interval logic in DOMTimer.cpp doesn't have any effect, because it's only applied to individual timers. If a site makes 1000 separate setTimeout() calls, they will all try to run at once.

I think all JS timers for a given ScriptExecutionContext should be throttled together. If I call setTimeout() 1000 times, we should stagger their start times by minimumTimerInterval().

We may also want to dynamically increase minimumTimerInterval() if timers are regularly missing their deadlines.

I'm happy to pick up this task, if nobody else is working on it.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.