[Webkit-unassigned] [Bug 23865] Safari can be frozen by rapidly adding timers

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 10 12:38:48 PST 2009


------- Comment #4 from darin at apple.com  2009-02-10 12:38 PDT -------
(In reply to comment #3)
> From looking at the code, it can be happening for a long time. Timers are
> implemented using CFRunLoopAddTimer. According to Apple docs, the run loop
> fetches the timers first and input second. So if there is always a timer ready
> to be scheduled/fired, no input goes through.

If that analysis is correct, then we do not need two timers in the test()
function to make this happen, as we don't need exponential growth to have the
problem. I suspect that's not the entire story.

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

More information about the webkit-unassigned mailing list