Bug 7318 – REGRESSION: Timer bug causes gif animation and (html and JS) page forwarding to fail

• Status: RESOLVED
• Resolution: FIXED
• Component: JavaScriptCore

[Jon]

On my quad, loading the test case for bug 5340 repeatedly will eventually stop the gif animation. When it is frozen, it affects all gif animations, even in other tabs. It also prevents html and JS powered forwarding, such as that happens when trying to go to apple.com/developer. Testing with various people in the IRC channel, and on my iBook 500, seems to indicate that this bug only affects multiprocessor machines over a certain clock rate show this bug. A dual 1.42GHz G4 was reported to exhibit this bug, but a dual 500 and dual 867 didn't. For now I'm assuming this is a timer bug since that seems to be the common element between the affected features, but I could be wrong. 

Essentially, reload the test case until it freezes, then no timers work at all, even for already loaded content.

This affects nightly r12858.

[Alexey Proskuryakov]

I'm also seeing this. Not sure if the issues aren't already tracked in bug 5340, though.

[Jon]

Based on discussion in #webkit last night it was determined that this is a separate bug. 5340 covers the partial animation of gifs when in different html structures. That bug still exists in 417.8. This bug pertains to the breaking of all gif animation and anything else that relies on a timer in ToT.

[Darin Adler]

Damn, must be a bug in my new timer implementation. Gotta see if I can reproduce it.

[Darin Adler]

I can reproduce this to. By adding logging, I've determined the problem is with the Macintosh implementation of the single shared timer. I'm going to change how that mechanism works to see if I can fix it.

[Darin Adler]

Created attachment 6611 [details]
create new timer each time since CFRunLoopTimerSetNextFireDate is failing

[Maciej Stachowiak]

Comment on attachment 6611 [details]
create new timer each time since CFRunLoopTimerSetNextFireDate is failing

r=me