Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

"Warning: Unresponsive script" message and Firefox v16+

  • 4 vastausta
  • 10 henkilöllä on sama ongelma
  • 6 näyttöä
  • Viimeisin kirjoittaja cor-el

more options

I recently upgraded to v16, and then v17. In both cases I repeatedly received the dreaded "Warning: Unresponsive script" message, so frequently that the browser became unusable.

https://support.mozilla.org/en-US/kb/warning-unresponsive-script

I reverted to v15 and now I NEVER get the "Warning: Unresponsive script" message anymore

Just so you know...

I recently upgraded to v16, and then v17. In both cases I repeatedly received the dreaded "Warning: Unresponsive script" message, so frequently that the browser became unusable. https://support.mozilla.org/en-US/kb/warning-unresponsive-script I reverted to v15 and now I NEVER get the "Warning: Unresponsive script" message anymore Just so you know...

Kaikki vastaukset (4)

more options

Try the Firefox Safe Mode to see how it works there. The Safe Mode is a troubleshooting mode, which disables most add-ons.

(If you're not using it, switch to the Default theme.)

  • You can open the Firefox 4.0+ Safe Mode by holding the Shift key when you use the Firefox desktop or Start menu shortcut.
  • Or use the Help menu item and click on the Restart with Add-ons Disabled... menu item while Firefox is running.

Don't select anything right now, just use "'Start in Safe Mode" To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before using the Firefox shortcut (without the Shift key) to open it again. If it is good in the Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one.

Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.

When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.

Muokattu , muokkaaja Jan.

more options

Do you remember which file (chrome:// URI) was causing the message?

more options

Evidently several addons were throwing the error, including NoScript, Tab Utilities, BetterPrivacy, Ghostery and RSS Ticker. These are "must have" addons for me, so disabling them is not an option.

I had previously researched all the possible solutions to this problem and found that none worked. Frankly I have tired of troubleshooting and have now resorted to reverting to the "Last Known Good Configuration" and will stick with it until such time that I have no option but to upgrade Firefox to a subsequent version. It ain't broke now, so I ain't gonna fix it. Cheers.

more options

You can still try to check out is one of those extensions is causing your issue.
Then you can contact the developer for advice or see if there is a development version of the extension available that fixes it.