Manually increment `i` because we break
FACEBOOK UNRESPONSIVE SCRIPT FIREFOX CODE
The only way to solve the problem for all users that might be viewing your page is to break up the number of iterations your loop performs using timers, or refactor your code so that it doesn’t need to process as many instructions. In general, delays between 50 and 100 milliseconds are appropriate and allow browsers enough idle time to perform necessary display updates.
FACEBOOK UNRESPONSIVE SCRIPT FIREFOX UPDATE
It’s recommended to never use a delay of zero milliseconds, as this isn’t enough time for all browsers to properly update their display. From there, either remove the offending piece of code or change it in such a way that it won’t be as resource intensive.Įven a very small timer delays can also cause the browser to become unresponsive. Checking the error console should make it pretty obvious what part of your JavaScript is causing the issue. Sometimes the message mentions at the dialog may not be the cause of the problem. To find the source of the problem and determine why the the script is running too long, click on the “Stop Script” button on the warning dialog, then open Error Console to see the cause of the script issue. The default maximum ( MaxScriptStatements) is 5,000,000 instructions, you can increase this number on a single machine by editing the registry. Specially in Internet Explorer(IE) this message displays when it reaches the maximum number of synchronous instructions for a single piece of JavaScript. In depth look at the unresponsive script error If it continues to run, your computer might become unresponsive. You can stop the script now, or you can continue to see if the script will complete.”Ī script on this page is causing your web browser to run slowly. “A script on this page may be busy, or It may have stopped responding.
In Internet Explorer, the script time-out value can be changed on specific client computers by modifying a registry entry. Therefore, you may want to increase the amount of time that passes before the message box appears. Some tests and benchmarks may use scripts that take a long time to run. 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.Īs per MSDN, some scripts may take an excessive amount of time to run, Internet Explorer prompts the user to decide whether to continue running the slow script. This time is given by the settings dom.max_script_run_time and dom.max_chrome_script_run_time. The major and common possibility is, when JavaScript code runs for longer than a predefined amount of time, you see a dialog that says Warning: Unresponsive Script. There are many reasons that may lead to raise unresponsive script error. As per Mozilla Knowledge-base, unresponsive script error appears with different web browsers including Internet Explorer, Google Chrome and Mozilla Firefox.
0 kommentar(er)
