Bug 137213 - Moving gif runs berserk
Summary: Moving gif runs berserk
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.5
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 137788 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-11-11 22:11 UTC by Niels
Modified: 2008-05-19 17:16 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Example (20.29 KB, image/gif)
2006-11-12 14:14 UTC, Niels
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Niels 2006-11-11 22:11:47 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages

On this page:

http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro/Advanced_Tutorials/Advanced_Animation/Guided_tour/Const/ik

are some moving gifs that make Konqueror use up all available CPU. GIMP shows them just fine.
Comment 1 Niels 2006-11-12 14:14:48 UTC
Created attachment 18510 [details]
Example

Here's an example. Gwenview shows it correctly, Konqueror doesn't.
Comment 2 Bram Schoenmakers 2006-11-12 18:19:42 UTC
Have you enabled Qt GIF support? Check if the useflag 'gif' was used for the qt package.
Comment 3 Niels 2006-11-12 19:18:20 UTC
Yes, I have that. Moving gifs usually shows fine, albeit not exactly as in Firefox.
Comment 4 Martin Koller 2006-11-13 15:33:45 UTC
Can confirm with 3.5.5 (CVS); konqueror and X use 100%CPU when showing above page.
Also, the animation on this page http://en.wikibooks.org/wiki/Image:C_ik.gif
is shown in konqueror much too fast (which I assume is the main reason for the 100% CPU).
Interesting effect: the first loop of all frames looks OK (in terms of speed), but then it seems to loop as fast as possible.
Comment 5 Bram Schoenmakers 2006-11-23 21:59:03 UTC
*** Bug 137788 has been marked as a duplicate of this bug. ***
Comment 6 Médéric Boquien 2008-05-18 20:09:41 UTC
Thank you for the bug report. It appears that the bug is no longer present in KDE SVN trunk (r809157).
Comment 7 FiNeX 2008-05-19 17:16:47 UTC
Confirmed on trunk, still present on 3.5.9.
Anyway the main trend seems that this type of bugs will not be fixed on the 3.5 branch.