RESOLVED DUPLICATE of bug 22280 Bug 24710
WebKit hangs when navigating page laden with large animated .gifs
https://bugs.webkit.org/show_bug.cgi?id=24710
Summary WebKit hangs when navigating page laden with large animated .gifs
Cabel Sasser
Reported 2009-03-19 19:15:49 PDT
Summary: When scrolling through a page with a lot of large, many-frame animated .gif's, latest WebKit nightly (and Safari 4 Beta) will to hang / freeze for a while. Steps to Reproduce: 1. Load the URL. 2. As the page loads, use the Page Up / Page Down keys or mouse to scroll through the page. 3. Most importantly, scroll to the bottom of the document, gradually. Then try scrolling back up. What's Expected: Scrolls like butter. What's Happening: As the page approaches / reveals post #39, which contains a repost of a large animated .GIF, the browser will begin to stutter. The spinning cursor will appear for seconds at a time, and appear to freeze. Eventually it might un-freeze, only to re-freeze later. In short, the browser becomes unresponsive.
Attachments
A sample during one of the "hangs" (43.20 KB, text/plain)
2009-03-19 19:16 PDT, Cabel Sasser
no flags
Cabel Sasser
Comment 1 2009-03-19 19:16:22 PDT
Created attachment 28778 [details] A sample during one of the "hangs"
Mark Rowe (bdash)
Comment 2 2009-03-19 23:30:38 PDT
Kevin M. Dean
Comment 3 2009-03-25 09:28:27 PDT
Mark DeBernardi
Comment 4 2009-05-11 14:48:37 PDT
Does not 'hang' WebKit, just takes up massive CPU processes the first time through the animation. Once the animation has played back once, it goes more smoothly, but still does not compare to playback in Firefox. For example, this 1.5M animated gif pegs the CPU at 100% and playback is jerky. http://i43.tinypic.com/16hqfdi.gif
Peter Kasting
Comment 5 2009-08-17 21:54:49 PDT
Yep, all given examples perform fine in Google Chrome 4.0.201.1, which uses WebKit trunk from a couple days ago, so this is almost certainly bug 22280. *** This bug has been marked as a duplicate of bug 22280 ***
Note You need to log in before you can comment on or make changes to this bug.