Closing a tab takes a loooong time, sometimes 10 or 15 minutes while Firefox is completely disabled, with one or more inactive script warnings.
Firefox is the only browser that behaves this way. Unfortunately, there are a number of Firefox extensions I can't do without. The newest version kills them all, and in fact, the latest "update" to version 52 ESR turned it into the current version, so I had to find a copy of the previous update and download it. Switching to the current version is a non-starter, as every reason I had to use Firefox in the first place has been eliminated from it.
All Replies (3)
It sounds like you want to stay with Firefox 52 despite the obvious security issues, but you have a problem with unresponsive script warnings.
Does anything in this article help: Warning Unresponsive script - What it means and how to fix it?
Does the problem occur with nonessential extensions disabled? By nonessential, I mean ones you can live without for eight hours.
Do you have Firefox set to keep history, so if you force-quit you can expect to do a crash recovery at the next startup?
I appreciate your response. I've tried disabling extensions, but I hadn't recently added any when this started anyway. The length of time FF is disabled depends on the size of the page. On a blog post with a lot of comments it can be 10 or 15 minutes, and it's just completely unresponsive, whether or not I get script warnings.
It's as if it has to "unwind" every page just to quit it. No other browser does this, and FF didn't do it until recently. Is the internet infested with some new, exceptionally virulent strain of Javascript?
If ESR 52 became updated to the newer ESR 60 version it could be that you ended up with updated versions of your extensions and the new versions of those extensions may not be compatible with ESR 52.
Any chance that the OSX Time Machine has a backup of your Firefox Profile from before the newer version became installed?