FF can be somewhat paranoid about "busy" scripts. Basically, it has a timer and if the script runs "too long", it complains. But it neglects to figure out "oh, wait, the script is running too long because I am running a bunch of stuff in the background". Ie, it is measureing 'real time' not 'cpu time of the script', so a slow or just plain busy machine will trigger it.
I get it periodically at slashdot when I have a bunch of things going on... I just click the continue and go on (it beats the old behavior where a loop in a script would drag the browser to its knees while it tried to figure things out..) -- snarlydwarf ------------------------------------------------------------------------ snarlydwarf's Profile: http://forums.slimdevices.com/member.php?userid=1179 View this thread: http://forums.slimdevices.com/showthread.php?t=59974 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
