Closed Bug 140243 Opened 22 years ago Closed 22 years ago

Scrolling Slow when resized GIF files appears on screen.

Categories

(Core Graveyard :: Image: Painting, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: zaw0, Assigned: pavlov)

References

()

Details

(Keywords: perf)

I was studying Pro/E and testing/using mozilla RC1 Released Built and I came
across the URL above. 

When you're scrolling the page with arrows or MWheel when you come across the
B/W Gif Images on this page Scrolling will become Jerky. The .gif files on pages
seem to be resized. Tried with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.0rc1) Gecko/20020425 and problem still exists.

I did extent search on bugbase already and if this is a dup bug I'm very sorry
to waste your time.
wfm 2002042023 on linux ppc
wfm 2002042603 on win2k
wft (Linux, 1.0RC1 on a Athlon 1000 and Linux, 0.9.9 on a Celeron 433)
Blocks: 100951
Severity: trivial → minor
Keywords: perf
WFM School machine. Windows NT 4.0 

Screen Rez 800*600 65K colors 75hz.

Home computer is 1152*1024 True Color 75hz and it scroll jerky when B/W gif
image appears on screen. Especially the L shaped braket.
WFM Mac OS X Mozilla 1.0 branch build 2002042605
 Zaw:
*lol*
ehr.. irgnore comment 6 *G*

i did read something different.. .. arg.. was to early in the morning.. damd
drugs ;)
Status update: This page WFM on 2002050504 win32 on win2kpro.
Replicated on Win2k, testcase follows:

http://www.llamasoft.co.uk/hb/hbhist.html
1) Load this page
2) Hold the down arrow key until the page scrolls down to the rotating cows at
the very bottom
3) When about the third row of cows begins to appear, the scrolling becomes
unbearably slow
Grah, add with 2002051006 1.0 branch (RC2) to that up there
I apologize for horrendously spamming this bug, but I've discovered the whole
reason why the slowdown occurs.

Get out the Task Manager (you can summon it up on Win2k with CTRL+ALT+DEL then
pressing the Task Manager button), set it to always on top and watch the
Performance tab.  Now open that test page and scroll down to the cows.  CPU
usage jumps to 100%, guaranteed. (My box: PIII 500 MHz, 256 MB RAM).

This is nasty, very very nasty.

Further, I tested this on RH Linux 7.1 with Moz trunk 2001070104 (old build,
yes, I know, but I don't have root here).  I used the KDE System Guard (which
gives you a graphical 'top' with CPU usage) and watched it at two positions on
the page:

Top of page while scrolling down:
mozilla-bin:  2.49% user, 0.74% system
X:            2.5% user, 0.5% system

Bottom of page, with the cows, not scrolling:
mozilla-bin:  14.86% user, 0.05% system
X:            70.30% user, 1.52% system

Regardless of platform, Moz's GIF rendering library seems to be having a jolly
old time spamming the window system while spinning the cows about.

OS -> All??
I use edit this page feature in mozilla and deleted the animated cows table.
Scroll the page within the Composer and it still slow down. When it get to this
image ( http://www.llamasoft.co.uk/hb/lsel.jpg ) which is rezied with html tag
("width="240" height="320" ) it will slow down.

On a Amd 700 256MB Windows 2000 with Nvida TNT2 Ultra. Using taskmanager
Performance TAB, CPU Useage while scrolling the number will jump up to 95% soon
as isel.jpg show up on screen. Displaying the looping animated cow use up 100%
of CPU too.
WFM with Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0+) Gecko/20020531   and RC3

Please have a look on bug 100951 !

Any problmes seen (with other OS) to set this bug FIXED or WFM?

Can we close this bug ?  keywords --> qawanted ?
It still doesn't work smooth on this computer.

build : 2002051006
reporter: does it still happen on 1.1beta?
no response from reporter for >60 days. resolving WORKSFORME.

reporter: if you can reproduce this with a recent build of mozilla, please
reopen this bug. thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.