539015 - The firefox.exe process will not end when browser is closed. When I try to re-open, it wont until firefox.exe process ends

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Robin Burgess]

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

When I press the "x" in the top right corner, Firefox closes but the
firefox.exe process is still running and consuming CPU usage. When I decide to
go back onto Firefox, I have to kill the firefox.exe process manually through
command prompt before it opens again. After doing this and Firefox opens again,
it ALWAYS asks to restore my previous session and that Firefox has updated to
3.5.7. This bug only occurs when Firefox has been opened and closed once. I am
running Windows XP Professional SP3.

Reproducible: Always

Steps to Reproduce:
1.Close Firefox browser by clicking "x"
2.Open Task Manager
3.Manually kill the firefox.exe process
4.RE-open The firefox browser
Actual Results:  
it ALWAYS asks to restore my previous session and that Firefox has updated to
3.5.7. This bug only occurs when Firefox has been opened and closed once.

Expected Results:  
Firefox should open with my homepage and not the above said and should not have to kill the process manually

Comment 1

[Paul O'Shannessy [:zpao] (not bugmail, email directly)]

Firefox is asking if you want to restore your session because it has some built in crash detection. So session restore knows that Firefox didn't quit cleanly.

To fix that problem we really need to figure out why you need to kill the process. A good place to start is checking extensions / plugins and/or starting in safe mode to see if the problem persists.

Comment 2

[Tyler Downer [He/Him]]

Ghostery is one addon that has been causing this, there are several others that have 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.

Comment 5

[Arthur K. (he/him)]

Similar to bug 503041, I am now seeing this behavior on the Fx29 RC. This wasn't happening in fx29.0b9.

Comment 6

[Arthur K. (he/him)]

I did observe this happen on Fx29.0b9 on a different machine.