Re: memcache.c internals question
| From: | Antony Dovgal | Date: | Tue, 24 Jul 2007 20:22:38 +0000 |
| Subject: | Re: memcache.c internals question | ||
| References: | 1 2 3 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-4820@lists.php.net to get a copy of this message | ||
On 25.07.2007 00:18, Ravi Menon wrote:
Hi Antony, Thanks for the quick response. I believe we have the latest code - version 2.1.2 tarball from the the pecl distribution. It has the 'Revision' field set to '1.80': php_info_print_table_row(2, "Revision", "$Revision: 1.80 $"); This is what 'php -i' output reports on our boxes. So regarding the dtor, I am aware that it may not be called during the end of request cycles, but is it guaranteed that it will never be called during memory pressure or any other scenarios where the garbage collector kicks in, across request cycles? Some of our php code is memory intensive.Sure, it's just impossible. But I don't really get what does this question to do with your problem. PHP/memcache most likely would segfault in such case, but that's not what you see.
The strange behavior in our system is that it recovers itself after a while without any intervention (it may last for minutes) but my guess here is that apache child max requests expires, and the new child spawned somehow sets everything right.That's quite possible.
I am planning to enable debugging and will try to get more info.Thanks! -- Wbr, Antony Dovgal