Closed Bug 47766 Opened 25 years ago Closed 25 years ago

Mozilla maxes out cpu when trying to scroll some pages.

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows 2000
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 43943

People

(Reporter: kberk.spamaway, Assigned: asa)

References

()

Details

I till try to come up with a more comprehensive list of sites with this problem, but in a nutshell here is what I am seeing: The progress meter at the bottom of the page is hanging on some sites (like the one mentioned above). It usually hangs at 98 - 100% but does not say document done and the bar looks like it is still working. When this condition exists, mozilla becomes very unresponsive, trying to scroll vertically causes the cpu to max out for a few seconds and mozilla eventually reacts to teh command. I have been seeing this quite a bit, I will see if I can update this with more sites that have the problem to help isolate the issue. I am using the M17 candidate build 2000080404 on Windows 2000 Server SP1.
With the latest M18 nightly (2000080508) on Win2k SP1, I do not have the hanging percentage problem, but I do see the EXTREMELY slow scrolling behaviour. When scrolling, mozilla is using 95%+ cpu. I doubt this is important enough to hold M17, so perhaps the reporter could try with the latest nightly to see if the hanging progress bar still occurs.
looks like a dupe of bug 43943 *** This bug has been marked as a duplicate of 43943 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
verf dupe
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.