108664 - Site makes mozilla consuming extensive cpu and memory

Status: RESOLVED DUPLICATE of bug 108637

(SeaMonkey :: General, defect)

Description

[Georg Wild]

From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.14-pre8 i686)
BuildID:    2001110601

When opening www.freshmeat.net, mozilla shows the site clearly, but just before
finishing it uses extensive cpu and makes more and more memory usage. So the
only way is to kill it.
First time writing this bug report with mozilla itself caused the same problem
when pressing "open bugzilla form"!

Reproducible: Always
Steps to Reproduce:
1.open www.freshmeat.net

Comment 1

[Karl Johan Kleist]

I don't see this using Build ID 2001 10 30 03 (Win2000),
so this may be regression?

Comment 2

[Asko Tontti]

Seeing with PC Linux 2001110610 (buildid is incorrect in mozilla.org's
early nightly build for Linux. This buildid should probably be 2001110606).

I see this hang also at

  http://www.slashdot.org/
  http://www.linuxtoday.com/

Comment 3

[Asko Tontti]

Commit button in this bug also caused hang and I see these problems also with
build PC Linux 2001110521.

Comment 4

[Peter Janes]

Similar behaviour clicking "Submit" on bugzilla.mozilla.org's "Vote for this bug" page.  Also Linux trunk build 2001110610.

Comment 5

[Stephen Moehle]

I see these problems with Windows 2000 and 2001110603.

Comment 6

[Asko Tontti]

This might be a dup of bug 108637.

Comment 7

[Jonathan Abbey]

I also see this CPU spin and no-refresh hang several
times when visiting www.aintitcoolnews.com with the
Linux 2001-11-06-10 build.  I kill the non-refreshing
main mozilla window with the window manager's window kill
function, and am left with several Mozilla threads, one
of which continues to spin and eat the CPU.

The same thing occurred to me when I tried to fill in this
bug report here on Mozilla.. am using Netscape 4.74 to
report this.

Comment 8

[R.K.Aa.]

a build frmo shortly before the fix for bug 107789 was backed out showed this
bug. A build from after the backout does not show the bug. It's a dup.

Comment 9

[Diego Biurrun]

*** This bug has been marked as a duplicate of 108637 ***