using yesterday's winXP trunk build, and going to Debug->Viewer Demos->#10 Anim Images causes the CPU on my 1.2Ghz, 256Mb ram, winXP machine. I don't recall this being expected behavior recently (I know we've gone through stages where this pages causes 100%, and stages where it doesn't). I also noticed that when dragging the window, or resizing it, animation stops.

->ImageLib

Still seeing this using win xp 2002122608 (1.01 Ghz machine)

still seeing on winxp build 2003011713

And still seeing this using win 2k 20030131 (Athlon 750, Riva TNT2) Someone'll profile it?

I only see 40% CPU usage with Phoenix 20030224, Windows XP, Dual Athlon 1700+, 1024MB DDR266 Reg ECC RAM, ATI Radeon 9700+

*** Bug 195864 has been marked as a duplicate of this bug. ***

still seeing on win2000 build mozilla 1.3

*** Bug 197672 has been marked as a duplicate of this bug. ***

-

In WinXP and Win2k Using Moz 1.4rc3 CPU pegs at 100% (1.7 & 2.53 pentiums on different machines). When I view the processes on task manager and kill the offending Mozilla process Mozilla seems unaffected, i.e. no windows close etc. I just noticed this problem and it may be on the Microsoft side, i.e related to an update.

How about with a recent build?

Tested on a recent build, and it doesn't seem to complete peg the machine, allthough CPU load is high (as to be expected with such animations)...

Modified version of test10 which will run on IE: http://mozilla.animecity.nu/test10.html Moz 20050105: 48% CPU IE: 44% CPU Win2k AMD Athlon XP 2500 Anyone still having this bug, please compare CPU usages with IE and Mozilla. Post your results here. This bug has been here long enough, if there's no one who can duplicate abnormal CPU usage, then I'll close it. Shall I give it a week?

Firefox 1.0: 12% Firefox 20050105: 8% IE 6.0: 5% WinXP SP2 / P4 2.8GHz

*** Bug 311694 has been marked as a duplicate of this bug. ***

*** Bug 311694 has been marked as a duplicate of this bug. ***

See comment #13. The link is no longer there, and no activity on this bug since that date, so this bug can be closed? Note, bug 311694 was actually solved by updating nVidia drivers...