284204 - 100% CPU hang on exit if a second window has been open

Status: RESOLVED DUPLICATE of bug 280427

(SeaMonkey :: General, defect)

Description

[R.K.Aa.]

2005022805 trunk
I've tested the three previous builds extensively and something this happens in
todays build that didn't happen in the previous builds:

After some times usage, Mozilla's CPU goes up to 99/100%. I haven't found a
pattern yet and only notice this because the fan is rarely running on this
computer, but today it has triggered three times because Mozilla is acting up
and the CPU is getting too warm.

In this CPU intensive mode: When i try to exit the application, Mozilla vanishes
from sight, but is still running in the background. Must be killed via taskmanager.

Filing as unconfirmed just to have it logged, in case a window comes in handy at
some point.

Comment 1

[Onkar Shinde]

(In reply to comment #0)

I faced the same issue with Mozilla 1.8b1 on Win2kSP4.
No fixed pattern.
Faced the issue two three times.


Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217

Comment 2

[R.K.Aa.]

I now found a way to reproduce the bug:

-Start Mozilla
-Open a webpage
-On that page, open a link *in new window*.
-Close the new window
-and then exit Mozilla all together by closing the first window

Result:
As the original window closes, task manager shows mozilla suddenly hogging all
CPU and the process does not terminate.

Comment 3

[R.K.Aa.]

behaves just like recent bug 280427 -> bug 280456

CC BZ - any idea what is happening here?

Comment 4

[OstGote!]

See recent Bug 283823 and Bug 283523 too.

Comment 5

[Boris Zbarsky [:bzbarsky]]

No ideas offhand....  If you kill a hung instance, does talkback come up, by
some chance?

Comment 6

[R.K.Aa.]

No sign of it

Comment 7

[R.K.Aa.]

Have yet to reproduce this with trunk 2005030105
Starting to think this has been around for a while and keeps resurfacing.
The CPU intensive hang in bug 280427 may well have been completely unrelated to
the crash in bug 280456

Comment 8

[R.K.Aa.]

with 2006030305 this happens all the time, also without having had a second
window open.

Comment 9

[R.K.Aa.]

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