Ghost browser in operation




9 years ago
8 years ago


(Reporter: jbdrvr, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2010-11-01])



9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2009032609 Firefox/3.0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2009032609 Firefox/3.0.8

I have a ghost browser in operation even when I've closed my browser. I've tried running the task manager to see if anything else is running besides the application I am working on but nothing shows up. I don't think I can re-create it because it's not part of a process I'm working on. I hear ads or infomercials in the background.

Reproducible: Always
What do you mean? Is there a firefox process running even after firefox is closed, or what?

Comment 2

9 years ago
Firefox seems to be running even after I've closed the browser. I hear it running in the background even when I have a clean desktop.
When you press CTRL+ALT+DELETE, and click on the processes tab, does firefox.exe show?

Comment 4

9 years ago

Comment 5

9 years ago
I can try it when it happens again.

Comment 6

9 years ago
It's happening again. I had to close the browser to make sure but firefox isn't in the processes.

Comment 7

9 years ago
see <>

(Bugzilla is not a support site, but a tool for developers)
This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile,, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.