249262 - Hangs on certain site

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Andy Bolstridge]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1

Viewing this page will often cause firefox 0.9.1 to hang

http://boards.fool.co.uk/Index.aspx

It doesn't happen for any page that is viewed, but over 10 viewings of the site,
it has hung firefox everytime eventually - usually takes a dozen messages to
stop responding (just browse some messages and you'll get it after a while).

CPU usage goes to 100%, the client area is completely frozen, but the main
window can be minimized etc. The status bar at the bottom shows 'transferring
data from g.boards.fool.co.uk....'


Reproducible: Always
Steps to Reproduce:
1. go to http://boards.fool.co.uk/Index.aspx
2. browse boards and messages
3. eventually (dozen messages usually, sometimes hangs on first page)

Actual Results:  
CPU usage goes to 100%, firefox atops responding.

Expected Results:  
work! :)

If you tell me how to enable debug, I'll see if I can get any more info for you
as this one is a bit vague.   I'm running vanilla 0.9.1 straight from the installer.

Comment 1

[Andy Bolstridge]

this is similar to bug #248270

Comment 2

[Daniel Kabs, reporting bugs since 2002]

I may add, it is also similar to bug #251412, as vague as bug #249638 and as
hard to reproduce as bug #248270. 

Granted, I use Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
but the engine is the same as Firefox, isn't it?

Comment 3

[Daniel Kabs, reporting bugs since 2002]

I've downgraded and now I'm using Mozilla/5.0 (X11; U; Linux i686; en-US;
rv:1.6) Gecko/20040113. 

I don't know what the equivalent Firefox version number is but anybody
experiencing this problem should downgrade to Gecko/20040113 and then try again.

Comment 4

[Andy Bolstridge]

Incidentally, since I upgraded 0.9.1 to 1.0PR I havn't seen this issue arise.

I guess that this bug has been resolved by another bugfix/change.

Comment 5

[Steffen Wilberg]

Don't resolve bugs as fixed if you can't point to a specific bug or checkin.

Comment 6

[Steffen Wilberg]

-> WORKSFORME.