Closed Bug 426427 Opened 16 years ago Closed 14 years ago

when exiting firefox3 it still runs in the background

Categories

(Firefox :: General, defect)

3.0 Branch
x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: mark0d0da, Unassigned)

Details

(Keywords: hang, Whiteboard: [closeme 2010-06-05])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008032504 Minefield/3.0b5pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008032504 Minefield/3.0b5pre

When i exit firefox3, it stills run in the background and i need to kill it manually, this problem is from firefox3 beta4, but its also in the nightly builds wich i currently use. also tried different pakages ( vanilla from firefox.com, swiftfox ) they also have that problem. Running archlinux up-to date

Reproducible: Always

Steps to Reproduce:
1.Start firefox3
2.Close it
3.Try to start it again
Does it also happen in the Firefox safemode ?
- http://kb.mozillazine.org/Safe_Mode
tried with safe mode, it also doesn't work. But i have run firefox from command line and firefox was still running in the command line although i have close all the windows. Also i tried with and without extensions, i always get the same result/
I have the same problem. I am running windows XP. After browsing the internet and shutting down firefox3.0.1, firefox continues to run in the background. I have to restart my computer to get firefox to work. Did not have this problem with firefox2.
do you still see this issue in Firefox 3.6 started in safe mode?
 http://kb.mozillazine.org/Safe_Mode
Keywords: hang
Whiteboard: [closeme 2010-06-05]
Version: unspecified → 3.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.x 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
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.