Support Article
"Stop running this script?" error in dev portal IE8/IE7
SA-1542
Summary
After appliying following hotfixes, we are getting javascript message:
Stop running this script?
A script on this page is causing internet explorer to run slowly.
if it continues to run, your computer may become unresponsive.
Occurs on IE7 and IE8 for only.
Hotfixes that were installed.
HFix-4995 Harness Buttons not displayed properly
HFix-8710 OnClick (single click) events from Report definition not working
HFix-9868 PRPC62SP1[UI]Navigation Rule not responding to keyboard events
HFix-9963 PRPC62SP1[UI]Expanded sections are not accessible via keyboard
HFix-9984 Notes not expandable via Keyboard commands
Error Messages
Stop running this script?
A script on this page is causing internet explorer to run slowly.
if it continues to run, your computer may become unresponsive.
Steps to Reproduce
Click anywhere on dev portal
Root Cause
** Investigation **
The customer implemented a solution found via the PDN ARTICLE:
https://pdn.pega.com/implementation-methodology-dco/how-to-prevent-ie-warning-stop-running-this-script-when-adding-application-requirements
Change IE -> Styles -> DWORD value for 'MaxScriptStatement registry value to 'to ‘FFFFFFFF’
Microsoft imposes a hard limit on the number of instructions that will get executed without returning control to the user. When that hard limit is exceeded, the popup results. It is know that PRPC will rarely resume proper execution after getting these messages.
The problem, is due to an excess of JS execution within the Browser. In the past, we have seen this caused by:
• Customer addition of key-stroke logging software which takes too many instructions to gather up information
• Frame resizing software which goes into a loop (not necessarily infinite)
• An excess of Rich Text Edit fields which are being refreshed.
• Recursive referencing within custom sections
• Text area initialization algorithms which are very compute intensive and sometimes cross the threshold
• An application with multiple tabs, none of which use deferred load, which just takes too many instructions to render.
The key factor is that all of the problems are wholly within the Browser, and leave no indications of anything wrong or notable that can be found by network traces, Fiddler traces, Tracer sessions.
**
Resolution
This issue is resolved by making the following change to the PRPC operating environment:
Combination of the registry changes as above and a complete DB cache clear.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.