[imp] Endless loop after imp upgrade 5.0.13 to 5.0.14

[LALOT Dominique]

2011/10/20 Martin Baum <pop3 at flachtaucher.de>

>
> Hi,
>
> after upgrading from imp-5.0.13 to imp-5.0.14 on a busy site I am seeing
> php-processes that get stuck in an endless loop until PHP max_execution_time
> is reached. Does anybody see the same behaviour?
>
> max_execution_time is reached in different parts of Tree.php so I am unable
> to locate the cause for this. Here goes my log:
>
>
> [20-Oct-2011 11:57:16] PHP Fatal error:  Maximum execution time of 300
> seconds exceeded in /path/imp/lib/Imap/Tree.php on line 1709
> [20-Oct-2011 12:30:08] PHP Fatal error:  Maximum execution time of 300
> seconds exceeded in /path/imp/lib/Imap/Tree.php on line 1279
> [20-Oct-2011 12:31:31] PHP Fatal error:  Maximum execution time of 300
> seconds exceeded in /path/imp/lib/Imap/Tree.php on line 829
> [20-Oct-2011 12:37:44] PHP Fatal error:  Maximum execution time of 300
> seconds exceeded in /path/imp/lib/Imap/Tree.php on line 1722
> [20-Oct-2011 13:00:56] PHP Fatal error:  Maximum execution time of 300
> seconds exceeded in /path/imp/lib/Imap/Tree.php on line 1277
>
> I only see this with live traffic and unfortunately I can not reproduce it.
> strace / ltrace for php-processes shows nothing so the loop does not call
> any syscalls oder libcalls.
>
> best regards,
> Martin
>
> --
> IMP mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: imp-unsubscribe at lists.horde.**org<imp-unsubscribe at lists.horde.org>
>

It's may be an effect about a big change in javascript code due to a search
bug in IE9 (solved in 5.0.14). I had to clear my browser cache in order to
get things running and all was fine. I don't know what could happened on a
busy server, but it's probably the cause of your problem.
Avoid the javasrcipt cache on the server side as it could be also a cause of
the problem.

Dom

-- 
Dominique LALOT
Ingénieur Systèmes et Réseaux
http://annuaire.univmed.fr/showuser.php?uid=lalot