806818 - Website hang 16.0.2

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[Hammerfest]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20121024073032

Steps to reproduce:

Went to: 

http://www.engadget.com/2012/10/29/iphone-5-giveaway/
or
http://www.engadget.com/2012/10/29/iphone-5-giveaway/#continued


Actual results:

Before it finish's loading, Firefox freezes up and stops responding (cant get it to generate a crash report) having to be force killed.
Firefox 16.0.2 (tested on 3 different system's, and on a clean profile)


Expected results:

Should have loaded ok...

I thought it was the livefyre comment system Engadget switched to, but it only crash's for me when I try to visit that particular page.


*I don't discount it could be a user issue even though I tried it on 3 different systems and with a clean profile on one system (with all plugins/extensions disabled), I probably haven't tried everything, but I haven't had a website kill Firefox since v4

Comment 1

[Scoobidiver (away)]

With a new profile in 16.0.2 or Nightly on 64-bit Windows (4GB of RAM), I got the unresponsive script prompt twice but the page finishes loading if I click Continue.

Comment 2

[[:Aleksej]]

A crash at least usually involves the window closing.  When the program is frozen, it’s a hang.

Comment 3

[Hammerfest]

Interesting, I never got an unresponsive script prompt, just crashed.

Ya, sorry for that, was in a bit of a rush, non-responsive hang, not crash.

Comment 4

[Scoobidiver (away)]

(In reply to Hammerfest from comment #3)
> Interesting, I never got an unresponsive script prompt, just crashed.
Are you sure the prompt is not hidden?

Comment 5

[Hammerfest]

I was never able to get an unresponsive script prompt, or any sort of useful report. By the time I went to try again on a fresh install'd PC, I had already updated to Firefox 17, and was unable to recreate the crash.

I did notice on the page that it froze up the browser up for a few moments in FF17, but it continued after only a few moments, so I cant tell if it was a website error specifically with Firefox (as it didnt happen in IE), or something with FF16.x

Needless to say, seeing as I dont have this issue any longer, I am changing it to resolved/closed.


Thanks for the comments, and of course, sorry I wasnt able to get the same scenarios that others did.