1022754 - Firefox hangs indefinitely, safe mode does not allow me to kill the offending site

Status: RESOLVED DUPLICATE of bug 516752

(Firefox :: Untriaged, defect)

Description

[Gail]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140506152807

Steps to reproduce:

Here is the site that hangs:
www.partsguy.com/products.html

I could not close the tab. Firefox froze with the message "Unresponsive". Restarting in normal mode, firefox remained frozen.
Starting in Safe-mode did not let me select the tab I wanted to kill.
It closed all the tabs and I have lost information. 


Actual results:

Firefox locked onto the last tab in a session. It hung. Then I could not kill the tab with the X or with short cut keys. Then starting in safe mode, I was unable to select the offensive tab and remove it. What is the point of safe mode if all you can do is kill all the tabs!


Expected results:

I should have been able to select the offending tab and remove it. I alternately use Chrome and Firefox. Neither are perfect, but Chrome has the better architecture.

Comment 1

[Paul Silaghi, QA [:pauly]]

(In reply to Gail from comment #0)
> Here is the site that hangs:
> www.partsguy.com/products.html
It doesn't hang to me, FF 30, Win 7 x64.
Please update to FF 30.
If you still reproduce this, try on a new profile
http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager

Comment 2

[[:Aleksej]]

firefox-30.0.en-US.linux64
No hang, but it made Firefox unresponsive for a few seconds while loading.

Comment 3

[Gail]

I updated Firefox to 30.0. The problem persists on my system, even after waiting 2 minutes. IMHO, a slow-loading site should not make Firefox hang or become unresponsive. Some way to close a particular tab needs to be built in. Apparently, Firefox can detect the situation because it shows the status message "Not Responding" when this problem occurs. The user should be offered some escape hatch at this point, the easiest being to kill the tab. If the user wants to hang out and wait for a page to load, he/she does not need to carry out the kill.

I finally used Task Mgr to kill Firefox. When I restarted, the session manager allowed me to remove the offending site from the list. Apparently, to do this you need to double click on the site you want to remove. There is no info on this feature and no remove button. But luckily, I just hit on it by trial and error. I will write this up as a separate bug.

Comment 4

[Matthias Versen [:Matti]]

>Some way to close a particular tab needs to be built in.
That developers are working on this for quit some time and the feature will come in some future versions.

I will mark this bug as dupe of the tracking bug for that feature