Is it possible to stop firefox linux sometimes leaving a running process after exit?
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.
Ñemoĩporã poravopyre
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.
Emoñe’ẽ ko mbohavái ejeregua reheve 👍 1Opaite Mbohovái (3)
Ñemoĩporã poravopyre
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.
Thanks philipp, useful answer much appreciated.
"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.