Firefox VS Ccleaner. WTF?

I click off the internet and close all my browser windows. ALL of them.

Half hour later I use Ccleaner and it tells me “Firefox is still open and running, shall it force Firefox to close?”

Huh?:confused:

I closed everything and 30 minutes later another program insists something is still open? It’s not, I assure you.

What the fuck is going on here?

You using Windows or Apple OS?

If you’re using Windows, hit Ctrl-Alt-Del or Ctrl-Shift-Esc and look at a list of the running processes. I bet Firefox really didn’t fully close up and you would have seen a “firefox.exe” running yet.

I get that message all the time. It’s a bug in Firefox. Scripts sometimes cause it to hang or close slowly.

Open task manager and you’ll see Firefox under the process list. Sometimes theres a container too. kill them. I have to do these at least twice a week. a pain in the butt.

Yeah, other than looking for “firefox.exe” in the Task Manager, also look for “plugin-container” and kill them manually if they don’t close by themselves after a few minutes.

Hmmm!

Thanks for the posts folks.:slight_smile:

In the future, is there anything I can do to prevent this, and have FF close when I click off?

When I use Firefox on my Winders XP mochine (rarely; I use Firefox on Linux mostly), from time to time I’ll close Firefox for some reason, and then try to re-start it soon, and I’ll get a little message saying that “Firefox is already running”. Then I have to wait a while (usually not too long) and try again.

I’ve seen that problem and it’s only one of several major issues that has led me to switch to Chrome because from what I can tell Chrome does not have THAT specific issue.

Instead of clicking on the red X to close FF, right click on the FF thingy on the bottom of the screen and select close. I am forced to use FF at work and this is how I get around that problem.

Every single time I start up Firefox it rells me ‘Firefox is already running’, then opens normally: same applies to Seamonkey ( Mozilla family too ). Even if I’ve closed it down completely from KSysGuard ( same as Task Manager ) — running OpenSuse 12.2.

I rarely close Fx, except by way of a Restart icon ( extension ) — in the latter case it doesn’t do this — since especially with Fx 18, Fx can open hundreds of tabs or just a few and all works fine; but a few hours in even without opening tabs or anything, it slows to molasses.

I tried Fx 19, and then found it just crashed at random; so backdated to 18. Then read some spokesman on Mozilla shouting at people never to do this because of ‘security’.

People always scream security to cover bad crap.

you can simply get into the habit of closing the firefox.exe directly through either CTRL+ALT+DEL or some other memory monitoring program like codestuff Starter that way instead of closing the program and THEN realizing you have to do the manual closing, it would also help you guarantee any wasted memory slowing down your computer for x amount of time before you finally realize it was open the entire time.

I had the same issue with Firefox on my system (Win 7 and 8, 64-bit). A few months ago, maybe a bit longer, I happened across a Firefox variant called Waterfox and tried that instead. It has never given me that issue, or the problem with container-plugin hanging either.

I am unable to say why this version does not hang like Firefox, but I am much, much happier with it. I presume others find the same results as I have, can’t point to ‘official specs/description’ about the issue being resolved.

It is only for 64-bit OS, though. Anyone with 64-bit Win that prefers Firefox should try out Waterfox - appears/works exactly like Firefox (all plug-ins work fine for me, fwiw) but without some of the Firefox issues, especially the ones listed here.

Pale Moon