Closed Bug 187559 Opened 22 years ago Closed 22 years ago

access4less.net causes big performance problem when scrolling (100% CPU jerky scrolling)

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 124150

People

(Reporter: pascalc, Assigned: asa)

References

()

Details

(Keywords: perf)

build 2002122808 WinXP

Steps :

1 go to http://access4less.net/
2 scroll the page

Expected result : smooth scrolling like in IE6
Actual result : scrolling is jerky with CPU jumping to 100% on a Athlon 1700XP/256MB

Problem reported on netscape.netscape7.windows apprarently there is a big
background image which may be the cause of the problem
Works fine here with 20021230 on Win 98.

CPU usage goes up to 25% on my Athlon 1200 with 256 MB RAM and a Nvidia graphic
card.

See also bug 124150.
The description of bug 124150 is similar but the url at this page does not
trigger the bug for me. I also have a nVidia card with the latest drivers, the
problem is more obvious when you use the mouse-scroll button. I've also noticed
that there is a one second delai to display the context menu or menu options on
this page while I don't have this problem with other pages in other tabs.
Perhaps the fact that I have a 1280x960 32 bits display puts a greater strain on
mozilla to redraw the page while it is scrolling.
Confirming using Mozilla 20030102 build here on P4 1.8Mhz/512Mb RAM/WinXP/nVidia
(latest WHQL drivers)/1280x960x32. There's no doubt the problem is caused by the
huge background image: 1200x5000 pixels. I've saved the HTML source locally,
removed the background attribute and I've put a <base href... to the original
site - there's no problem.

The URL of Bug 124150 scrolls faster although it is sluggish too and continuous
scrolling causes 100% CPU usage on the same system mentioned above.

*** This bug has been marked as a duplicate of 124150 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.