542652 - Firefox won't quit on close.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Mark Gailey]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)

After closing Firefox window and waiting four plus hours, when I try to
restart Firefox, it says it is still running and I must quit first. 
Task Manager is the only solution. This is a hassle. Why doesn't a close
window stop the process?

This has been the case for the last two updates.

Browser Details: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)
From URL: http://hendrix.mozilla.org/


Reproducible: Always

Steps to Reproduce:
1. Start Firefox
2. Close Firefox
3. Restart Firefox
Actual Results:  
Error message says Firefox still running, Task Manager confirms.

Expected Results:  
Task Manager process kill required.

Closing should quit.

Comment 1

[Jo Hermans]

This is not a support website, please see <http://support.mozilla.com/en-US/kb/Firefox+hangs#Hang_at_exit>. In particular, check your add-ons.

Comment 2

[Tyler Downer [He/Him]]

Do you have ghostery installed? Try safe mode as well.

Comment 3

[Tyler Downer [He/Him]]

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

Comment 4

[Tyler Downer [He/Him]]

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.