[PHP] Re: Segmentation fault in php5-imap

2008-12-29 Thread ceo
Perhaps compile everything in debug versions and get some core dumps and file a bug report at http://bugs.php.net/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

[PHP] Re: Segmentation fault in php5-imap

2008-12-24 Thread Dan Osipov
I just tried closing the message box and reopeining it, ie using imap_open & imap_close repeated, instead of imap_open, imap_reopen repeated, imap_close. Unfortunately, the server has a limit on the number of connections per minute, so I couldn't use that method... I am implementing some condi

Re: [PHP] Re: Segmentation fault in php5-imap

2008-12-23 Thread Nathan Nobbe
On Tue, Dec 23, 2008 at 5:30 PM, Dan Osipov wrote: > Script takes about 5 minutes to run (average). On other servers I've seen > it run over 2 hours without segfaults... All depends on how many messages > are in the NNTP mailboxes. ok, so this is def a long running script then. After applying

[PHP] Re: Segmentation fault in php5-imap

2008-12-23 Thread Dan Osipov
Script takes about 5 minutes to run (average). On other servers I've seen it run over 2 hours without segfaults... All depends on how many messages are in the NNTP mailboxes. After applying the mentioned patch to libc-client2002edebian the issue persisted. No change... I'm not running xdebug

Re: [PHP] Re: Segmentation fault in php5-imap

2008-12-23 Thread Nathan Nobbe
On Tue, Dec 23, 2008 at 1:42 PM, Dan Osipov wrote: > Everything matches. The only thing that's different is that the server > that's having the problem has been running the script every 15 mins for the > past 2 months - which leads me to believe there might be a memory leak > somewhere... if th

[PHP] Re: Segmentation fault in php5-imap

2008-12-23 Thread Dan Osipov
Everything matches. The only thing that's different is that the server that's having the problem has been running the script every 15 mins for the past 2 months - which leads me to believe there might be a memory leak somewhere... Although complete recompiling should reset something, right? I