I have seen that there are many questions about dealing with unresponsive scripts, scripts that stopped responding, script busy, for various programs. Entering "script st… (funda kabanzi)
I have seen that there are many questions about dealing with unresponsive scripts, scripts that stopped responding, script busy, for various programs. Entering "script stopped responding" produces 1000 results.
So this seems to be a general problem, and is not tied to any program (though my problem lately is gmail).
It's very annoying to have to wait until the script problem gets to the point where all open windows freeze, slow down, move in jerks rather than smoothly, without knowing what is causing the problem, since it seems that a script problem can happen with just about anything you want to do.
What I want to know is whether there is a way to set up some sort of automatic system to deal with it.
Something like "if a script is unresponsive for X amount of time, stop the script". Ideally with that amount of time being less than the amount of time it takes for the unresponsive script to interfere with all functioning.
Or some way to limit its disruption to just the window/application with the problem - so if gmail is having the problem, youtube or nytimes.com will not be affected.
Even an early warning system would be nice, like a message popping up identifying the application with the script issue and that it is going more slowly than it should.
I am no expert, but I am thinking that most of the applications or activities involving scripts should work within a few seconds. If this is the case, a pop up saying, for example "a gmail script has been spazzing out for 15 seconds now".
Basically, anything that sends an alert or that stops the problem before it affects the entire system would be very very helpful.