Closed Bug 272465 Opened 20 years ago Closed 19 years ago

Mozilla FF stops responding for around 30 seconds when rendering the page (100% CPU usage), IE renders the page OK without stopping

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED EXPIRED

People

(Reporter: crion, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041109 Firefox/1.0 (MOOX M2)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041109 Firefox/1.0 (MOOX M2)

Mozilla FF stops responding for around 30 seconds when rendering the page (100%
CPU usage), IE renders the page OK without stopping

Reproducible: Always
Steps to Reproduce:
Reproduced with: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

The page has a section at the bottom with ~8000 links, which is my guess for the
performance problem. This needs either duping or a profile.
I concur: this behaviour also occurs for me, with 

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

After many seconds, the browser returns to normal performance.

(I also regularly observe a similar, but distinct, performance problem where FF
simply crawls at a very slow pace, chewing up 99% of CPU, until all tabs/windows
are closed the process exits.  I haven't been able to spot the pattern yet -- it
doesn't seem to be page specific (the problem sometimes starts when viewing
pages I use frequently without problems), and typically only happens after it's
been running for a while with many tabs/windows.)
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.