Javascript hang in one FF window kills all other FF windows

RESOLVED INCOMPLETE

Status

()

Firefox
General
RESOLVED INCOMPLETE
8 years ago
7 years ago

People

(Reporter: Charles Harrison, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2011-1-30], URL)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.9.2) Gecko/20100115 Firefox/3.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.9.2) Gecko/20100115 Firefox/3.6

Throwing out a hung script in one FF window loses all others.

Reproducible: Always

Steps to Reproduce:
I have an infinite loop or similar in some javascript which I need to debug.  If I try and do it in FF, when the script hangs and the CPU maxes out, I can't close the tab, so instead I have to throw out FF with Task Manager, thus losing all the other tabs I was using.

Perhaps that is only to be expected, but ...

If I put the script in a second FF window all on its own, and I can't close it, when I throw it out with Task Manager, I also lose the original window with all my work.

Different FF windows should not share codespace or other memory.  They should be entirely seperate processes.

Actual Results:  
All FF windows are lost

Expected Results:  
Only the errant window should be lost (preferably only the errant tab).

I can't debug this Opera or IE, because the problem is related to asynchronous script loading, and they behave differently (and work).
You need to run with -no-remote and a different profile for each instance. See https://developer.mozilla.org/En/Command_Line_Options
(Reporter)

Comment 2

8 years ago
Thanks for the suggestion, which is helpful.  However, it's not enough.  Today, I had a hang, closed the debugging version, but the CPU was still maxed out.  It was only after I closed the main version and all versions in TaskManager that the CPU load returned to normal.

Despite the above precautions, there still seems to be some sort of interaction between the two windows, and this is highly undesirable.  One of the aims of a good OS is to ensure that when one thread crashes, it doesn't bring down others as collateral, but however good the OS is, it's all for nothing if the programmers' of apps deliberately to share code between windows.  For security and stability, seperate versions of an app running in different windows should be kept entirely apart.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.