MozillaZine

Unresponsive Script Warning

From MozillaZine Knowledge Base

(Difference between revisions)
Revision as of 16:36, 11 August 2012
Limpet235 (Talk | contribs)
(Finding the source of the problem)
<-- Previous diff
Revision as of 13:54, 15 October 2012
Wsm (Talk | contribs)
(simplify, clarify, generalize firefox specific language)
Next diff -->
Line 1: Line 1:
-When JavaScript code runs for longer than a predefined amount of time, Firefox will display a dialog that says ''Warning: Unresponsive Script''. This time is given by the settings [[dom.max_script_run_time]] and [[dom.max_chrome_script_run_time]]. Increasing the values of those settings will cause the warning to appear less often, but will defeat the purpose: to inform you of a problem with an extension or web site so you can stop the runaway script.+When JavaScript code runs for longer than a predefined amount of time, you see a dialog that says ''Warning: Unresponsive Script''. This time is given by the settings [[dom.max_script_run_time]] and [[dom.max_chrome_script_run_time]]. Increasing the values of those settings will cause the warning to appear less often, but will defeat the purpose: to inform you of a problem with an extension or web site so you can stop the runaway script.
-::Complete Error Message: “A script on this page may be busy, or It may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.”+Complete Error Message:
 +::“A script on this page may be busy, or It may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.”
-::Sometimes you may be able to identify the extension:+::Sometimes the message an extension, which may or may not be causing the problem:
::"Script: chrome://fastdial/content/storage.js:71" ::"Script: chrome://fastdial/content/storage.js:71"
 +
 +Anything that causes the mozilla application to slow down can cause this warning to be issued. The slowdown could be caused by an extension, but it might also be a web page, another program, or resource utilization (CPU, memory, disk IO) at levels high enough to impact one or more application.
==Finding the source of the problem== ==Finding the source of the problem==
-To determine what script is running too long, click the Stop Script button on the warning dialog, then depending on your version, go to Tools > (Web Development) > Error Console. The most recent errors in the Error Console should identify the script causing the problem.+ 
 +Click the Stop Script button on the warning dialog, then depending on your version, go to Tools > (Web Development) > Error Console. The most recent errors in the Error Console will identify the script that was running. But note, in some cases the add-on/extension causing the problem is not the one identified in the messages.
==Extensions== ==Extensions==
-If you get the Unresponsive Script Warning on many different web pages, the problem is most likely a recently installed [[problematic extensions|extension]].[http://help.yahoo.com/help/uk/toolbar/toolbar-54.html] You can try uninstalling extensions to fix the problem, or try [[Profile_Manager#Creating_a_new_profile|creating a new profile]].+Unresponsive Script is often caused by a recently installed [[problematic extensions|extension]], or an update to the extension or application thus causing some incompatibility between the two.
-;Some extensions reported having Unresponsive Script Errors +===Disabling extensions or rebuilding a new profile===
 +Several techniques can be used to identify bad extensions. A quick test is to start in [[Safe mode]]. If it works better in safe mode, then start in normal mode and try disabling/uninstalling extensions to fix the problem - either one at a time, or in groups. To do this in groups, disable half of the extensions and if failure continues, disable the other half. Enable and disable addons in successively smaller groups until reduced to just one extension that fails. Or try [[Profile_Manager#Creating_a_new_profile|creating a new profile]]. If the new Profile works correctly, then you can migrate specific files: [http://kb.mozillazine.org/Migrating_settings_to_a_new_profile] and reinstall extensions.
 + 
 +===Some extensions reported having Unresponsive Script Errors ===
* A9 Toolbar [http://kb.mozillazine.org/Problematic_extensions] * A9 Toolbar [http://kb.mozillazine.org/Problematic_extensions]
* Adobe Reader (update Adobe Reader) [http://forums.mozillazine.org/viewtopic.php?f=38&amp;t=624589&amp;start=0&amp;st=0&amp;sk=t&amp;sd=a] * Adobe Reader (update Adobe Reader) [http://forums.mozillazine.org/viewtopic.php?f=38&amp;t=624589&amp;start=0&amp;st=0&amp;sk=t&amp;sd=a]
Line 27: Line 34:
* McAfee Spamkiller [http://forums.mozillazine.org/viewtopic.php?f=39&amp;t=563596&amp;start=0] * McAfee Spamkiller [http://forums.mozillazine.org/viewtopic.php?f=39&amp;t=563596&amp;start=0]
* Unshorten v1.3 [http://forums.mozillazine.org/viewtopic.php?f=38&amp;t=883525&amp;start=0] * Unshorten v1.3 [http://forums.mozillazine.org/viewtopic.php?f=38&amp;t=883525&amp;start=0]
 +* Yahoo Ask toolbar [http://help.yahoo.com/help/uk/toolbar/toolbar-54.html]
* YouSendIt [http://lifehacker.com/162574/put-off-firefox-15s-unresponsive-script-dialogue] * YouSendIt [http://lifehacker.com/162574/put-off-firefox-15s-unresponsive-script-dialogue]
-===Disabling extensions or rebuilding a new profile===+===Websites===
-There are several techniques that can be used to identify bad extensions by disabling or rebuilding.+
- +
-*Disabling half of the extensions in a bad group of extensions, until reduced to one extension that fails and would be left disabled waiting for an update or uninstalled. Don't immediately reinstall all the other disabled extensions, use a little care and just restore half of the others, if good then restore the other half. +
-*Rebuilding a new Profile: [http://kb.mozillazine.org/Creating_a_new_Firefox_profile_on_Windows] -- If the new Profile works correctly, then you can migrate specific files: [http://kb.mozillazine.org/Migrating_settings_to_a_new_profile] and reinstall extensions.+
- +
-==Websites==+
If you get the Unresponsive Script Warning on a specific web page, it could be a problem with the JavaScript on the web page. You may want to contact the webmaster of the site to inform them of the problem, or you may wish to file a Tech Evangelism bug report. [http://www.ruzee.com/blog/2006/07/unresponsive-firefox-scripts-and-ruzeeborders/ Steffen Rusitschka suggests using setTimeout] on web pages that need to execute JavaScript for long periods of time. If you get the Unresponsive Script Warning on a specific web page, it could be a problem with the JavaScript on the web page. You may want to contact the webmaster of the site to inform them of the problem, or you may wish to file a Tech Evangelism bug report. [http://www.ruzee.com/blog/2006/07/unresponsive-firefox-scripts-and-ruzeeborders/ Steffen Rusitschka suggests using setTimeout] on web pages that need to execute JavaScript for long periods of time.
-===Updating Java===+==Updating Java==
[http://www.java.com/en/download/installed.jsp Updating Java] seems to have helped the following pages. Note Java is not the same as JavaScript. [http://www.java.com/en/download/installed.jsp Updating Java] seems to have helped the following pages. Note Java is not the same as JavaScript.
* iCloud.com with Firefox 8 and "Find My Phone" [https://support.mozilla.com/en-US/questions/894834] (Updated to Java Version 6 Update 30) * iCloud.com with Firefox 8 and "Find My Phone" [https://support.mozilla.com/en-US/questions/894834] (Updated to Java Version 6 Update 30)

Revision as of 13:54, 15 October 2012

When JavaScript code runs for longer than a predefined amount of time, you see a dialog that says Warning: Unresponsive Script. This time is given by the settings dom.max_script_run_time and dom.max_chrome_script_run_time. Increasing the values of those settings will cause the warning to appear less often, but will defeat the purpose: to inform you of a problem with an extension or web site so you can stop the runaway script.

Complete Error Message:

“A script on this page may be busy, or It may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.”
Sometimes the message an extension, which may or may not be causing the problem:
"Script: chrome://fastdial/content/storage.js:71"

Anything that causes the mozilla application to slow down can cause this warning to be issued. The slowdown could be caused by an extension, but it might also be a web page, another program, or resource utilization (CPU, memory, disk IO) at levels high enough to impact one or more application.

Contents

Finding the source of the problem

Click the Stop Script button on the warning dialog, then depending on your version, go to Tools > (Web Development) > Error Console. The most recent errors in the Error Console will identify the script that was running. But note, in some cases the add-on/extension causing the problem is not the one identified in the messages.

Extensions

Unresponsive Script is often caused by a recently installed extension, or an update to the extension or application thus causing some incompatibility between the two.

Disabling extensions or rebuilding a new profile

Several techniques can be used to identify bad extensions. A quick test is to start in Safe mode. If it works better in safe mode, then start in normal mode and try disabling/uninstalling extensions to fix the problem - either one at a time, or in groups. To do this in groups, disable half of the extensions and if failure continues, disable the other half. Enable and disable addons in successively smaller groups until reduced to just one extension that fails. Or try creating a new profile. If the new Profile works correctly, then you can migrate specific files: [1] and reinstall extensions.

Some extensions reported having Unresponsive Script Errors

  • A9 Toolbar [2]
  • Adobe Reader (update Adobe Reader) [3]
  • AutoAdd (use QuickAdd instead) [4]
  • Extended Cookie Manager [5]
  • Fast Dial, delete the Fast Dial folder and reinstall [6]
  • Febe [7]
  • FoxyProxy when using GMail [8]
  • Gladder conflicts with UpdateScanner 3.0.4. When you open a page from UpdateScanner Firefox hangs for awhile[9]
  • Lazarus: Form Recovery, fixed in 3.0 see author's homepage if not yet at add-ons.
  • [Beta] Phoogle (Google) Map Mod 0.4.0 [10]
  • Media Player Connectivity [11]
  • MobWars scripts, try reseting your boss database. [12]
  • McAfee Spamkiller [13]
  • Unshorten v1.3 [14]
  • Yahoo Ask toolbar [15]
  • YouSendIt [16]

Websites

If you get the Unresponsive Script Warning on a specific web page, it could be a problem with the JavaScript on the web page. You may want to contact the webmaster of the site to inform them of the problem, or you may wish to file a Tech Evangelism bug report. Steffen Rusitschka suggests using setTimeout on web pages that need to execute JavaScript for long periods of time.

Updating Java

Updating Java seems to have helped the following pages. Note Java is not the same as JavaScript.

  • iCloud.com with Firefox 8 and "Find My Phone" [17] (Updated to Java Version 6 Update 30)

Webroot Spy Sweeper

The Webroot Spy Sweeper application can cause an Unresponsive Script Warning on certain web pages. Try disabling or uninstalling the application, then clear cookies for the related websites. [18]

Finding similar problems

Finding others with similar problems may find something that helps.

  • Google Groups search in last three months for script on page is busy
  • Google web search in last three months for script on page is busy

See also

External