same as 239223 Zombie firefox process grows instead of dying.




9 years ago
7 years ago


(Reporter: Robert Wyatt Davis, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2011-2-15])



9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20091016 Firefox/3.5.4 GTB6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20091016 Firefox/3.5.4 GTB6 (.NET CLR 3.5.30729)

Appears to happen after a script fails to respond.  After stopping script
(or at least using the popup to try) and closing firefox, taskmgr shows the
firefox process growing instead of dying. this continues until system becomes unresponsive. after restart the error log shows an error but it is not the same
each time so I suspect there is an addressing error somewhere. the last script failure for me occurred on the new tab page. firefox will not restart until
zombie is killed by taskmgr.

Reproducible: Sometimes

Steps to Reproduce:
1.wait until a script fails
2.stop script
3.exit firefox
4 check taskmgr
I don't think this could be the same as bug 239223, as that is a meta. Did you mean another bug? If so, please mark this a duplicate of it. if there is already a bug on something, there is no need for another.

Comment 2

9 years ago
I don't think this is the same bug,this is another bug i can confirm it had the same problem,after stopped a script i got the same problem after closing firefox.

Comment 3

9 years ago
The symptom of Firefox failing to exit after all windows are closed is the same as 239223 which is the oldest open bug I could find with this symptom. It is associated with a script failure so the real problem may be aggravated by a javascript error handler. the firefox error console lists uncaught exceptions from different places so I am guessing addressing errors from a memory leak or an uninitialized parameter. If you mean by a meta bug one that is derivative from another bug then it is possible this is one. I am not familiar with that jargon.  I think from some of the discussions this failure to die and clean up is a commonly reported item with suspicion that it has multiple causes.  I think the script connection may be an important clue.  also the growing size of the process after it was supposed to die may be a clue. BTW firefox does not restart on its own which would be evidence of a Trojan cause.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
Whiteboard: [CLOSEME 2011-2-15]
No reply, INCOMPLETE. Please retest with Firefox 4 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: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.