New
#1
Actually, not just the last few versions. Been happening since the multiple processes was introduced way back. It's a timing issue, and how you have the setting.
It can occur if you start FF again to soon after shutting it down, and all the processes haven't quite finished closing out. It won't always happen, but is more like to happen on a FF stop and quickly restart it.
All theses processes have to shutdown and do whatever they do.
Reducing the number can help, but it's still a timing issue if you're too quick to re-start FF.
10 minutes is a bit excessive. I know Chrome has background apps that can still run unless you tell it not to. I don't think FF does. No, just looked, nothing similar to that in FF. Maybe some extension you have that's running something. Guessing blindly. For most, it's all those processes closing.
I only use one extension, Dark Reader. It probably is this DDR3 old memory. I know about the Chrome leftovers, I use it it Linux and I always say no. When my new machine gets here it will be better. Yes this has been going on since Firefox started the multi process thing, but has gotten worse for me with each new Windows 10 release. When I used Fx in Linux, this never happened.
Agreed, perhaps further back than I can recollect but in the last few revs it is a real PITA, especially after they added new features.
I found this but it doesn't do anything for me:
"Firefox is already running but is not responding" error - How to fix | Firefox Help
Mozilla really needs to fix the issue. Happens when Firefox is not even invoked for a minute.
Hi Compumind. I think all of us who have used Firefox for a long time have experienced or heard about that issue. This issue has been around forever and there is no established or standard fix. In fact, there is no official fix from Mozilla.
But I am going to tell you what I think you should look at. I took a look at the antivirus in your signature. I see you have Windows defender and Norton. Windows defender is not going to create this problem, but Norton? it wouldn't surprise me if as a test, you uninstall Norton and immediately afterward, the issue goes away completely.
Do the same test with other real time scanners if you are using any. Test running Firefox without them. And see if the issue goes away.
Despite this issue being fairly common for Firefox users, I never experience it in my computers. In my computers the issue just doesn't happen. I think the reason for that is because I don't use AV or real time scanners. My recommendation to check Norton is based on my personal experience using Firefox and what I know antiviruses do when you close programs. Like I said, it wouldn't surprise me any if uninstalling Norton fixes your problem.
Bo