Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

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.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

After FF 37 update, I'm getting many unresponsive (chrome) script errors.

peterallcdn
peterallcdn
more options

Hello,

My copy of Firefox had been running fine, then all of a sudden it started throwing Unresponsive Script errors. These errors possibly started after updating to FF 37/37.0.1.

The errors are for chrome elements, so extensions. When launching firefox, it's very sluggish. It takes 45s to display tab titles and favicons, 1m 15s to display the first script error and about 1m 45s before it loads its first page in a tab.

In the attached image, you can see the error for Classic Theme Restorer. Before it, there would be an error for Tidy (HTML?) but I disabled that extension to see if it'd prevent the script error. It does, but I don't want to have to start disabling all my extensions because of something gone wrong in firefox itself.

Looks like the image may not attach, so here's the error: "Warning: Unresponsive Script A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: chrome//classic_theme_restorer/content/overlay.js:2191 Continue - Debug script - Stop script"

Any idea why chrome/extensions unresponsive script errors would just start showing up?

I'm using Firefox 37.0.1 on Windows 8.1.

Thanks!

Hello, My copy of Firefox had been running fine, then all of a sudden it started throwing Unresponsive Script errors. These errors possibly started after updating to FF 37/37.0.1. The errors are for chrome elements, so extensions. When launching firefox, it's very sluggish. It takes 45s to display tab titles and favicons, 1m 15s to display the first script error and about 1m 45s before it loads its first page in a tab. In the attached image, you can see the error for Classic Theme Restorer. Before it, there would be an error for Tidy (HTML?) but I disabled that extension to see if it'd prevent the script error. It does, but I don't want to have to start disabling all my extensions because of something gone wrong in firefox itself. Looks like the image may not attach, so here's the error: "Warning: Unresponsive Script A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: chrome//classic_theme_restorer/content/overlay.js:2191 Continue - Debug script - Stop script" Any idea why chrome/extensions unresponsive script errors would just start showing up? I'm using Firefox 37.0.1 on Windows 8.1. Thanks!

All Replies (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

If you have Firefox set to show a home page or restore your previous session at startup:

Could you test starting up with a blank page? You can use the run dialog (somewhere on the screen with all the small program icons). Type or paste the following and press Enter or click OK: 

firefox.exe "about:blank"

Any difference? If needed, you can restore your previous non-private windows manually from the History menu > Restore Previous Session.

Do you recall any other software changes? These might include system updates, hardware device driver updates (especially graphics cards), or plugin updates (e.g., Flash) that occurred around the same time.