Subscriber Richard Fuller wrote from New Zealand (not Australia, as I mistakenly wrote in an earlier article) to ask about a fairly common problem.
Our web browsers (IE, Firefox, Chrome, Opera, Safari, etc.) receive, interpret and run the scripts — and sometimes, something goes wrong…
Recently I’ve been getting this type of message at frequent intervals:
Warning: Unresponsive Script.
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.
The options are "Continue" or "Stop Script", but the message doesn’t mean a lot to me and I’ve no idea which option to take. To add to the confusion it doesn’t seem to make any noticeable difference which I choose.
Have you any idea why these annoying messages keep cropping up? My computer’s old and tired, but I make sure to clean it up every night by deleting temp. files and running CHKDSK and RegistryFix. Once a week I run Raxco PerfectSpeed and do a disk compression. Until now this has seemed to keep it struggling along at a tolerable pace.
OS is WinXP Home SP3.
Your advice would me greatly appreciated, as always.
I wrote back to Richard to tell him that he had a good question — and it’s one that almost every computer user has seen.
Unfortunately, the problem was that this error can be caused by any number of things, such as:
- bugs in the script
- script waiting on input from the web server
- data transmitted from web server didn’t get received by web browser
- script received input from web server, but didn’t handle it
- data was received, but script didn’t process data properly
- script is waiting for input from you, but input dialog box is beneath one or more windows on the desktop
- … you get the idea.
The best fix, when you get this error, is to: exit IE/Firefox/Opera/Chrome/Safari (whichever you were using) and start it again. The error is usually a one-time problem.
Thanks, Terry — a typically unhelpful Microsoft feature, then. Very grateful for your advice.
Richard may be right, or may not, about the error message being a Microsoft feature.