[dev] Warning: Unresponsive script
Michael M Slusarz
slusarz at horde.org
Sun Dec 10 20:56:35 PST 2006
Quoting "eculp at encontacto.net" <eculp at encontacto.net>:
> Quoting Michael M Slusarz <slusarz at horde.org>:
>
>> Quoting "eculp at encontacto.net" <eculp at encontacto.net>:
>>
>>> With horde/imp cvs head I'm seeing the following message consistently.
>>>
>>> ----------------------------------------------------------------------
>>> | 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. |
>>> | |
>>> | | Continue | | Stop Script | |
>>> ----------------------------------------------------------------------
>>>
>>> The response becomes very, very slow prior to the JS message.
>>> After it speeds up for a bit and the cycle is repeated.
>>>
>>> Is anyone else seeing this?
>>
>> No. On which pages are you seeing this?
>
> I can't really tell. The machine becomes slow and when I would like
> to pick it up and throw it out a window I get the message. :(
>>
>> You may also want to do a shift-refresh (or whatever your preferred
>> method of clearing your cache) to make sure you have the up-to-date
>> JS files.
>
> I do that, restart apache, etc. etc. Nothing seems to fix it.
> After sending the email I decided to try something different, rather
> than use the server as my work station, I moved to another machine
> and haven't had any problems. I'm setting here watching a "top" on
> the server and it hasn't had any issues at all. Now I may have a
> work-around and I probably shouldn't use my unix servers as
> workstations but I've been doing it for over 20 years with no issues
> until now and in my opinion they should not have problems. I'm
> going to continue to try and track this down, if anyone else sees
> this please let me know.
This has nothing to do with your servers. The slow script your
browser is bugging you about is a slow javascript script running on
the client (i.e. browser) machine. So it has nothing to do with
apache, IMAP servers, etc.
If you want to try to debug locally (since apparently I nor any of the
other devs are seeing this behavior), if using firefox you can install
firebug (http://www.getfirebug.com/) and see which script is causing
problems - it sounds like one of the scripts is entering a infinite
loop but, again, I have no idea why/where this would be happening
because I do not see it myself.
michael
___________________________________
Michael Slusarz [slusarz at horde.org]
More information about the dev
mailing list