• Error message: A script on this page is causing Internet Explorer to run slowly
• Because some scripts may take an excessive amount of time to run, Internet Explorer prompts the user to decide whether they would like to continue running the slow script.
• Some tests and benchmarks may use scripts that take a long time to run and may want to increase the amount of time before the message box appears.
• In Internet Explorer, the script time-out value can be changed on specific client machines by modifying a registry entry.
There are situations when a Web page contains script that takes an unusually long time to run. If you are scripting an ActiveX control on a Web page to transfer a very large file or do a large database query, this will often cause a significantly long delay in this case is about to increase the recordcountlist in the web.xml file to 256 per customer request.
Workaround / Fix
Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it.
To change this time-out value in Internet Explorer 4.0, 5.0, 6, 7, or 8, follow these steps:
1. Using a Registry Editor such as Regedt32.exe, open this key:
Note: If the Styles key is not present, create a new key that is called Styles.
2. Create a new DWORD value called MaxScriptStatements under this key and set the value to the desired number of script statements. If you are unsure of what value you need to set this to, you can set it to a DWORD value of 0xFFFFFFFF to completely avoid the dialog.
By default the key doesn't exist. If the key has not been added, the default threshold limit for the time-out dialog box is 5,000,000 statements for Internet Explorer 4 and later.
Because the Internet Explorer 4.0, 5.0, 6, 7, and 8 time-out is based on the number of script statements executed, the time-out dialog box will not display during ActiveX control or database-access delays. Endless loops in script will still be detected.
For more information go to