Since the latest update I've been getting "Firefox not responding" more frequently than ever, and on more than one machine.
Anyone else having thes problems?
lucy24
11:03 pm on Jul 26, 2017 (gmt 0)
Mac or Windows?
tangor
5:37 am on Jul 27, 2017 (gmt 0)
None, problems that is. Delete (or disable) all plugins. Do a refresh Firefox.
Then ONE AT A TIME add back any plugins by the MOST NEEDED first philosophy. Most likely it is a plug in that is giving problems.
Win7pro 64 Running FF 54.0.1 64bit (plugins installed: NoScript, Better Privacy, Ad Block+, Theme Font Changer)
One to kill JS twice, one to clear all LSO, one to kill ads the other missed, and one so these aging eyes can see what the heck just happened. All of these are in current update with the present FF release cycle. If you are using anything else, drop back a version and don't update until the plugins do.
Win10 users might have a completely different experience
keyplyr
5:44 am on Jul 27, 2017 (gmt 0)
Use Chrome :)
(sorry, couldn't help it)
tangor
7:01 am on Jul 27, 2017 (gmt 0)
You're forgiven. Second best (tech wise) always has to try harder.
Chrome, however, has something FF does not have: A bill board on every g property urging chrome use. Meanwhile, niche FF (which it is becoming) can be the better browser (few resources, faster, more js support) and not worry about being #1, merely better.
keyplyr
7:04 am on Jul 27, 2017 (gmt 0)
Chrome59 benchmarks faster than the latest FF.
tangor
7:19 am on Jul 27, 2017 (gmt 0)
Not in all cases, but so close no cause to fiddle faddlel. You win. Chrome is faster. (IE whoops! (IE ACTUALLY beat both for JS JIT compiling, but who considers that?), not worth arguing about, but you do seem awful bent on selling chrome day in and day out).
CHROME WINS!
And we'll let it go at that.
engine
7:33 am on Jul 27, 2017 (gmt 0)
This is for Windows 10. It includes standard and developer editions. I already use Chrome, Vivaldi, and occasionally Edge, amongst others. There are few plugins running, and there are no plugins that are on all machines running Firefox. The consistent thing is Firefox.
tangor
7:57 am on Jul 27, 2017 (gmt 0)
What version? Are you on the beta? What plugins for FF (if any?)
keyplyr
8:02 am on Jul 27, 2017 (gmt 0)
I updated FF but only used it for a few minutes, then back to Chrome.
I don't remember getting that intermediate message "checking plugins and extensions for comparability" like I used to see in earlier updates... so maybe it is an extension compatability issue.
Have the machines with FF issues updated to Creators?
engine
8:21 am on Jul 27, 2017 (gmt 0)
This machine is on 54.0.1, and there are currently no plugins. Other machines are on the same version, but have varying plugins.
Windows 10 Creators.
It could, of course, be something such as a memory issue.
I'm hoping that it's just something that will resolve itself with the next update.
keyplyr
8:31 am on Jul 27, 2017 (gmt 0)
One one machine, you could try removing FF, then manually deleting your Mozilla profile, then restarting Windows, then reinstalling FF.
engine
9:03 am on Jul 27, 2017 (gmt 0)
I suspect i'm going to have to do that with each machine, one at a time.
tangor
9:00 am on Jul 28, 2017 (gmt 0)
Curiosity question: how many tabs open ROUTINELY? 1-10? More?
Same behavior on all machines?
If one machine when was the last time you had your ram chips checked? (Tested for all 8/16/32 gbs each?)
One of my machines routinely pharted, but only after the ram in use exceeded x and crashed into a fractured memory area. Replacing the stick fixed the problem.
engine
10:09 am on Jul 28, 2017 (gmt 0)
Some more than ten tabs, others no more than ten. Yes, same behaviour, all machines.
This is what's making me think it's a FF problem, perhaps the way it uses memory on the newer versions.
keyplyr
6:51 pm on Jul 28, 2017 (gmt 0)
FF just updated to 54.0.1 on one of my machines. Maybe that will fix the issue engine?
