402443 - Firefox.exe process in Task Manager, restarts itself when killed

Status: RESOLVED WORKSFORME

(Toolkit :: Startup and Profile System, defect)

Description

[Anthony]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9

Since installing the last release of Firefox, I have been seeing an extra firefox process in Task Manager that uses 3.4kb of RAM. I have tried terminating the process and tree, reinstalling, etc. This process still comes up no matter what I do. It interferes with updates, causing them to fail due to running process, so I must constantly kill it manually when updating. v2.0.0.9 has not stopped this issue. When initiated, the process hits the DNS server and stays active until the computer is shut down. Again, when terminated, it auto-starts again.
I would appreciate it if you would at least email me an option to stop this troublesome issue if not fix it altogether. (Comodo is convinced it's a virus or malware/spyware, though everything I've run thus far has refuted this claim.)


Reproducible: Always

Steps to Reproduce:
1.Restart Computer
2.Kill Process
3.
Actual Results:  
As stated above, the annoying process restarts.

Expected Results:  
How the hell should I know?


Ug, think it's all in the general description. I use no themes, no background, screensaver. Only Comodo Firewall Pro and WinRam Turbo. Oh, also F-Prot Antivirus.

Comment 1

[Jesse Ruderman]

Sure sounds like malware to me.  Does Task Manager give you a way to determine the full path of the program so you can differentiate two firefox.exes on your machine?

Comment 2

[Jesse Ruderman]

http://kb.mozillazine.org/Firefox.exe_always_open

Comment 3

[Anthony]

The above link to the Ivy trojan information was successful in removing my problem, though everything I tried failed to identify the trojan, including the new Comodo BOClean 4.25. Thanks much J.R. for that link and subsequent eMail. :)

Comment 4

[Jeremy Baron]

This bug is NOT FIXED.  FIXED requires that there be some identifiable change to the product's code which resolves the issue.

Comment 5

[Anthony]

(In reply to comment #4)
> This bug is NOT FIXED.  FIXED requires that there be some identifiable change
> to the product's code which resolves the issue.
> 

Perhaps you missed the previous post... The problem is not a bug with Mozilla, it's a Trojan virus, which cannot be corrected by any code change, thus the problem is FIXED.

Comment 6

[Anthony]

(In reply to comment #4)
> This bug is NOT FIXED.  FIXED requires that there be some identifiable change
> to the product's code which resolves the issue.
> 

Perhaps you missed the previous post... The problem is not a bug with Mozilla, it's a Trojan virus, which cannot be corrected by any code change, thus the problem is FIXED.

Comment 7

[Carsten Book [:Tomcat]]

hey anthony, its works for me, because the "Fixed" Status mean in Bugzilla that a code change in a Mozilla Product (like Firefox) was done to fix this problem.

For other problems like in your case with a Trojan its in Bugzilla "works for me", because the problem was resolved without a change in Firefox.

Comment 8

[Anthony]

UG! There is no way to correct the code in this case in order to resolve the issue, so it makes no sense to post it as anything other than FIXED.

Have it your way though, maybe an admin with a brain will have sense enough to change it to something reasonable and lock the damn thread.