FF Not Responding

[ColColt]

It seems for at least the past couple weeks I'll get a "Firefox is Not Responding" 3-7 times a day...so aggravating. I use to get the box that gave the choice of stopping the Script or not but I got tired of seeing that so often so got rid of it.

I've got the latest and greatest version of FF so what's going on and can it be cured?

 

[Melchior]

YUP!! its been happening to me very often too.

when you say " latest and greatest version of FF" I take it you have the "release build" which would be v54.0.1
yeah I read some where its a JavaScript BUG in FF that has has been fixed in v55

it IS TOTAL HELL FOR THE JS mess that is Facebook... it looks up so often for me I use the built in restart function

FILE-MENU --> "Restart" which is 2nd from the bottom of that menu list... It might be because of the FF ext.
- Classic Theme Restorer
that I have said "Restart" menu entry...


"got rid of it."
how did you do that??

....oh right the check box.. lol

 

[ColColt]

That is the version I have. I don't recall previous version causing this much trouble...waiting on ver 55.

 

[Melchior]

waiting on ver 55.

pretty much all we can do...
BUT why they don't release this fix with say FF v54.0.2 is a mystery???

anyway according to:
https://wiki.mozilla.org/RapidRelease/Calendar
the next release of Firefox is scheduled for (August-08-2017)(FF v55)

 

[ColColt]

Exactly-they know the problem. Hopefully, the fix is indeed just around the corner.

 

[Melchior]

Exactly-they know the problem. Hopefully, the fix is indeed just around the corner.

yeah :sarc: just NOT soon enough... uggh!

 

[ColColt]

Agreed-I wait with keen anticipation.

 

[mrjimphelps]

I also have the latest version of FF, although mine is for Linux, not Windows. But I almost never, if ever, get these sorts of error messages. Perhaps you should install the FF add-on NoScript. Here is my experience with NoScript:

Once you have installed it, set it to not allow anything. Then begin surfing the web. When you get to a website, NoScript will tell you what is trying to run. You can then either temporarily or permanently allow whatever scripts you want, or leave them blocked.

Even though the problematic script is facebook.com, and I allow facebook.com scripts, I never get this message when I do Facebook.

Some scripts have to run. For example, if you are doing online banking, you need to let the scripts run which pertain to your bank's web site.

You will be amazed at how much faster some web sites run. You will also be shocked at how many scripts are trying to run on most websites.

There are some scripts that you have to let run, or you won't be able to do hardly any surfing. For example, google.com. But I don't let any other google scripts run, only those with google.com. Also, for Facebook (and other sites), you need to allow facebook.com and fbcdn.com.

If you will be patient and will fine tune NoScript, you will find that you don't see these "script" messages very often, and that your surfing is fast.

 

[ColColt]

Here's the kicker-FB is the only place I have this problem. Seems a known glitch exists and FF is taking it's precious time fixing it.

 

[SIW2]

No Script doesn't help this issue on windows.

 

[ColColt]

Keeping my fingers crossed FF will apply a fix to the problem soon.

 

[mrjimphelps]

Perhaps you could downgrade to a previous version of FF which didn't have this problem. Or try Opera.

 

[ColColt]

From what I understand they're in the process of upgrading soon(1st week of August?). Maybe the fix will work. The problem is primarily on FB.

 

[Melchior]

then again.. why didn't they release the patch for Facebook's JS HELL with (v54.0.1) or with a new (v54.0.2)???