firefox is open but not responding
I recently began having this issue with Firefox running in the background after closing the browser. Issue is intermittent but it occurs more often than not. Issue can occur by simply opening Firefox and then closing it without visiting any website - my default homepage is about:blank.
This issue began immediately when I updated Firefox from 24 to 25. The extensions I have are Noscipt, Adblock Plus and Fireshot. All are very popular. It appears that if I disable all extensions, then the issue doesn't appear. But if I add one of the above extensions, the issue appears. Therefore, it doesn't appear related to any specific extension - just the fact that there is any extension.
When I uninstalled Firefox 25 and reinstalled Firefox 24, the issue disappeared. When I updated to Firefox 25 through the upgrade process, or even through a direct 25 install without going through 24, the issue reappeared.
What is interesting is the issue does not occur every single time nor is it connected to any one specific extension or profile as I created a new profile and only imported my bookmarks.
Chosen solution
After disabling the Clear History on Close option as suggested by someone on mozillazine.org, so far, it appears that has resolved the issue for me as many opening/closing of Firefox has worked 100% since disabling that feature.
But good luck getting the Firefox team to fix that feature that they apparently broken in an update. If I seem disgruntled, it's because I had to go through a lot (new profile, clean install, etc., etc.,) only to find it never fixed the issue while still seeing responses that it must be a browser add-on and not Firefox issue despite a growing amount of people have reported the issue directly related to the 25 update.
I'm still going to use Chrome more than previously because of this experience and it apparently being Firefox and not some add-on.
Note from moderator: Since the thread owner reported in this post that the issue has been resolved, I've marked this post as the solution. aw
Read this answer in context 👍 1All Replies (6)
When it does occur you need to manually terminate the process in task manager. Their is no fix yet for the stable release but i am using aurora and haven't encountered this issue since updating from 25.0.
Modified by user991771
But I shouldn't have to do that, right? Chrome and any other program I use in Windows doesn't require force-closing in the Task Manager. Been a Firefox user for years and did not have to do that on a regular basis like I now need to for 25.
I've not seen any official report from Firefox taking some accountability for this issue as an official bug - just the usual reply of trying Safe Mode and it being an AV, Firewall, or Extension issue.
Yes i agree, you shouldn't have to do that. The only advice i can offer is using Aurora which is an experimental build or you will have to manually terminate Firefox whenever you encounter that.
To update, I still have this issue with Firefox needing to be terminated in the Task Manager despite another Firefox update to 25.0.1. I didn't have this issue prior to 25 and I been using Firefox for years.
I don't ever use Private browsing but I do use the Adblock extension and I clear history upon exist. I could not really trace it to the Adblock extension as it appears any extension at all may triggers the issue. The hassle of a new profile and simply importing bookmarks didn't fix the issue. My Firefox is also set to open to about:blank.
Been using Chrome more and more because this issue is an annoying experience with Firefox - regardless if it's Firefox or the popular extension Adblock.
There's a growing amount of people reporting this same issue with 25 over at mozillazine.org
Chosen Solution
After disabling the Clear History on Close option as suggested by someone on mozillazine.org, so far, it appears that has resolved the issue for me as many opening/closing of Firefox has worked 100% since disabling that feature.
But good luck getting the Firefox team to fix that feature that they apparently broken in an update. If I seem disgruntled, it's because I had to go through a lot (new profile, clean install, etc., etc.,) only to find it never fixed the issue while still seeing responses that it must be a browser add-on and not Firefox issue despite a growing amount of people have reported the issue directly related to the 25 update.
I'm still going to use Chrome more than previously because of this experience and it apparently being Firefox and not some add-on.
Note from moderator: Since the thread owner reported in this post that the issue has been resolved, I've marked this post as the solution. aw
Modified by AliceWyman
Just to say I've had no problems at all with Firefox 26. It's now been 10 days since I downloaded and installed it and not one 'Firefox is already running, but is not responding' error.