755160 - Application still remain on memory even after it's closed.

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[arrivu]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0
Build ID: 20120420145725

Steps to reproduce:

I closed the Firefox application. It happens at my home and office PC. Both running on Windows 7.


Actual results:

The application still remains on memory as a process.


Expected results:

The process should have been closed once I close the application.

Comment 1

[Andre Klapper]

Hi arrivu. Thanks for taking the time to report this!
Does the problem still happen if you start Firefox in Safe Mode? (Safe Mode disables extensions and themes, hardware acceleration and some JavaScript stuff in order to exclude some possible reasons for problems. It does not disable plugins which are add-ons.) See http://support.mozilla.com/en-US/kb/Safe+Mode 

And does this also happen with a new and empty profile? See http://support.mozilla.com/en-US/kb/Basic%20Troubleshooting#w_8-make-a-new-profile and http://support.mozilla.org/kb/Managing%20profiles . 

If you still see this problem in the new profile, please enter the address "about:support" in the address bar and attach (using the "Add an attachment" link above) the output for your original profile (not the new profile), as the "Modified Preferences" section could be interesting. 
Thanks for your help!

Comment 2

[Jason Smith [:jsmith]]

Robert - Do you know who would be the right person to look into something like this? This is related to closing firefox on windows and the application process still running after close.

Comment 3

[Robert Strong (they/them - no direct email)]

Triagers at this time. Without more info it is pretty much impossible to figure out what code needs to be investigated and from that which dev should investigate the code where this is happening. The first step would be for the reporter to perform the steps in comment #1 or similar steps (e.g. safe mode, disabled plugins, etc.) but there will likely be many more steps to perform after that. One example where this has happened previously a plugin was at fault.