Helping people with computers... one answer at a time.
Dear, Leo. I use both Firefox and Chrome. Often, I get the message, "The following script is busy. You can either continue or stop." And in the top, it shows "Firefox's not responding." In Chrome, I get the message, "The following pages are unresponsive. You can either kill or continue and the system hangs. What could be the reason? Is it something to do with my system?
Typically not. This is usually the side effect of how a web page has been written and what it's trying to do.
So at that point, you have two possibilities.
You can say, "Well, okay," and wait for the script. Maybe it really is taking too long on purpose. Maybe it really is doing something valuable.
On the other hand, you can say, "Nope, I'm impatient. Kill the script. Let's get on with our lives."
Now, there are scenarios where it actually, very legitimately, can take too long. I see it all the time and quite frankly, I'll usually let a script continue to run - because it's usually because of a very benign (and very common) reason that it's just taking longer than normal. An example: again, Facebook.
When the script is out there it's basically going out to Facebook and asking, "Is there something to update?" If there is, I'll get it, I'll display it, and I'll wait a few seconds; and then I'll go back for an update, I'll display it, and wait a few seconds.
Now, what happens if when that script starts, it asks Facebook, "Is there an update?" and it doesn't get a response?
Well, it waits for the response. The script is still running, but the script is waiting for a response. If it waits too long, then your browser says, "Hey, this script is still running. It's unresponsive."
The script is very legitimately waiting for something but that "something" is simply taking longer than it normally does. It may be the case that the response will come back from Facebook that says, "Yep, here's some data to be updated." And the script will continue on; it will carry on. It will grab the data; it will display it; and so forth. It just took longer than normal. Long enough that the browser seemed to care.
So, there's really no one size fits all answer for this.
Sometimes, scripts simply take longer than the browser expects them to. Therefore, you get this particular message to basically give you the option of killing what might be a hung script.
It might not be; it might be something very valid, but there's no easy way for you and I to tell.
My advice is to let it wait.
It'll complain again... if the script stays unresponsive, the browser will complain again. If it complains a second time then, you know, yea, I might go ahead and kill it. But for the most part, I've seen enough things (especially with these kinds of online interactive updating kinds of scripts, that you do find in sites like Facebook and Twitter and Gmail and so forth) that sometimes things just take longer than you expect and it's probably worth it letting them continue to try for awhile.
If you get fed up... Sure, go ahead and kill 'em.
Next from Answercast 55 - Can I use this other Windows XP Setup Disk on a different computer?
Comments on this entry are closed.
If you have a question, start by using the search box up at the top of the page - there's a very good chance that your question has already been answered on Ask Leo!.
If you don't find your answer, head out to http://askleo.com/ask to ask your question.