Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Is it possible to stop firefox linux sometimes leaving a running process after exit?

  • 3 réponses
  • 3 ont ce problème
  • 1 vue
  • Dernière réponse par Derek C

Derek C
Derek C
more options

I run Firefox 29.0-5.fc19 on a fully updated Fedora 19 OS with the KDE Plasma desktop. When I want to listen to the BBC iplayer radio service, I open firefox and go to the site http://www.bbc.co.uk/radio4 and click on 'Listen Live' and a pop-out player spawns and begins playing. If I don't want to browse anything else, I close the main firefox browser leaving the pop-out (child) firefox window playing the live BBC radio stream. But, if I then close this pop-out, I then find I cannot re-start Firefox because error message says firefox is already running.

To restart the browser, I have to use ksysguard to kill the running firefox process - usually around 120,000K in size - first.

I this a known bug? The only solution seems to be to run another firefox main window before closing the iplayer pop-out player, and then close the main firefox. It's an issue because I don't always remember to go through this rather arcane way of doing things.

I run Firefox 29.0-5.fc19 on a fully updated Fedora 19 OS with the KDE Plasma desktop. When I want to listen to the BBC iplayer radio service, I open firefox and go to the site http://www.bbc.co.uk/radio4 and click on 'Listen Live' and a pop-out player spawns and begins playing. If I don't want to browse anything else, I close the main firefox browser leaving the pop-out (child) firefox window playing the live BBC radio stream. But, if I then close this pop-out, I then find I cannot re-start Firefox because error message says firefox is already running. To restart the browser, I have to use ksysguard to kill the running firefox process - usually around 120,000K in size - first. I this a known bug? The only solution seems to be to run another firefox main window before closing the iplayer pop-out player, and then close the main firefox. It's an issue because I don't always remember to go through this rather arcane way of doing things.

Solution choisie

hello, unfortunately this is currently a bug in the current firefox version when you have set your history to be cleared at firefox shutdown (under options > privacy) - that is investigated and in the process of getting fixed by mozilla's developers with a high priority.

Lire cette réponse dans son contexte 👍 1

Toutes les réponses (3)

philipp
philipp
  • Moderator
more options

Solution choisie

hello, unfortunately this is currently a bug in the current firefox version when you have set your history to be cleared at firefox shutdown (under options > privacy) - that is investigated and in the process of getting fixed by mozilla's developers with a high priority.

Derek C
Derek C Auteur de la question
more options

Thanks philipp, useful answer much appreciated.

Derek C
Derek C Auteur de la question
more options

"unfortunately this is currently a bug in the current firefox version when you have set your history to be cleared at firefox shutdown"

I'll just change my settings until the bug is fixed.

Should I mark this as solved? It answers my specific question and offers helpful advice so logically yes, even though it refers to an as yet unfixed bug.