210047 - hang with 100% CPU usage

Status: RESOLVED DUPLICATE of bug 210119

(SeaMonkey :: General, defect)

Description

[Steve Thomas]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030619 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030619 Mozilla Firebird/0.6

Within a few seconds of accessing http://www.gameplay.co.uk (whether by bookmark
or typing in address bar) FB hangs with 100% CPU (Gameplay does not display
anything). Clicking the close icon [X] appears to close FB but process is still
runinng and needs to be killed (Windows 2000 SP2).

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Erik]

I can confirm this using both SeaMonkey and MozFirebird Gecko/20030619 on
Windows NT 4.0 - so if at all, this is a SeaMonkey issue.

Since we already have some bugs filed related to this page this might be a
regression - unfortunately I'll have to call it a day now so someone else might
have a closer look on this.

=> adding 'regression' 

Comment 2

[Tom Sommer]

This also happens a *wide range* of other sites.

Comment 3

[Michael Lefevre]

this is probably a dupe - not sure what of though.  not Firebird-specific anyway...

Comment 4

[Stephan Jaensch]

I can reproduce this with Firebird 20030620 under Linux. OS -> All.

Comment 5

[baffclan]

Reproduced with 2003062004-trunk/Win2k.
But, cannot reproduce 2003062104-1.4/Win2k.

Comment 6

[Erik]

I can confirm comment #5: it's working now using SeaMonkey Gecko/20030622, but
it's still broken using Moz.Firebird Gecko/20030622 on Windows NT 4.0. 
I used the provided URI from the bug report since this was the only page where I
encountered this problem.

Comment 7

[hub-san]

Both on Linux and on MacOSX, I can't confirm this bug using 2003061808-trunk. 
But, I confirm this bug using 2003061908-trunk.  This problem occurred within
between 20030618 and 20030619.  Unfortunately, I confirm this bug using
20030621-trunk/MacOSX.  Plus, using MozillaFirebird-2003062208/MacOSX, too. 
BTW, Bug 209979 sounds like this bug.  I think these bugs happened in the same day.

Comment 8

[Erik]

Is there anyone left who is able to reproduce this using latest SeaMonkey or
MozillaFirebird (e.g. MacOSX or Linux)? At least on my box with NT 4.0 both
browsers work fine now using the 2003-06-23 build whereas the 2003-06-22
MozillaFirebird build showed the problem...

Comment 9

[Boris Zbarsky [:bzbarsky]]

darin, does your header-parsing patch fix this by chance?

Comment 10

[Stephan Jaensch]

Can't reproduce this with a 20030624 Linux Firebird build anymore.

Comment 11

[hub-san]

I can't reproduce with 2003062403-trunk(MacOSX).
I think this bug probably was related to bug 210119.

Comment 12

[Erik]

Resolving duplicate of bug 210119 per comment #9 & comment #11.

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