This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Why is the Firefox process still running after quitting the browser?

  • 3 răspunsuri
  • 37 au această problemă
  • 4 vizualizări
  • Ultimul răspuns de tylerk1369

more options

Ever since the newest update, 29.0.1, the Firefox process continues to run after quitting the browser. To reopen the browser, I need to terminate the process in the task manager which is kind of annoying. I have tried all of the fixes that have been suggested in other articles without any success. Has anyone else had this issue with the newest update?

Ever since the newest update, 29.0.1, the Firefox process continues to run after quitting the browser. To reopen the browser, I need to terminate the process in the task manager which is kind of annoying. I have tried all of the fixes that have been suggested in other articles without any success. Has anyone else had this issue with the newest update?

Toate răspunsurile (3)

more options

What did you try so far?

A possible cause is using "Clear history when Firefox closes" to remove personal data when you close Firefox, so you can try to disable this feature.

more options

I have been using the clear history feature for years now without any problems. I did try eliminating that feature but the problem still persists. Is there anyway it could be from the most recent update? I have tried updating my Java plugin, turning it off, and the other options from the article Firefox hangs after quitting it.

more options

Has anyone else had this issue with the new update and found a solution?