Re: how to find a memory corruption in php ?
| From: | Pierre Joye | Date: | Fri, 01 Apr 2011 13:20:31 +0000 |
| Subject: | Re: how to find a memory corruption in php ? | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-51789@lists.php.net to get a copy of this message | ||
hi,
In php 5.3+ the memory limit default is 256MB, not 128MB. 5.3 does not
necessary use more memory but actually uses and reports its usage more
efficiently. I would suggest to use this default value and try again.
About detecting leaks and memory corruptions, valgrind is a good tool
to begin with.
Cheers,
On Fri, Apr 1, 2011 at 1:27 PM, Pascal COURTOIS <courtois@templeet.org> wrote:
> Hi all,
>
> I get an error with my program:
> Fatal error: Allowed memory size of 134217728 bytes exhausted at
> /home/courtois/php-5.3.6/Zend/zend_execute.h:163 (tried to allocate 261900 bytes) in
> /var/www/dev4.sociatomdev.com/chroot/htdocs/templeet/fetch.php on line 580
>
>
> - The same error occurs with any of php 5.3 versions tested. With 5.2 it's ok.
> - I know the error message is wrong. The program does not consume much memory.
> - If i change some lines in my php code like adding trace messages it sometimes work sometimes
> no (but constant result for same php code)
>
>
> I will not submit the bug since it's hard to reproduce unless being in the exact same
> configuration as me.
>
> I used to be an experienced C programmer (>300000 lines written) but almost nothing for the
> last 15 years.
>
> My questions:
> - is there any document somewhere to read before hunting a bug in php ?
> - are there any build/compile options other than --enable-debug ?
> - how should I proceed to debug when php is called via fastcgi ?
>
> My configuration: debian squeeze i386 32bits
>
> Thanks,
>
> Pascal
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org