Re: php cli memory leak error
| From: | Lewis Wright | Date: | Thu, 19 Feb 2009 13:19:01 +0000 |
| Subject: | Re: php cli memory leak error | ||
| References: | 1 2 3 4 5 6 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-288599@lists.php.net to get a copy of this message | ||
2009/2/19 Jochem Maas <jochem@iamjochem.com>:
> Thodoris schreef:
>>>
>>>
>>> seems to work fine here.
>>>
>>> What are your php.ini (memory related) settings?
>>>
>>> run:
>>>
>>> /usr/local/bin/php --ini
>>>
>>> and get the location of the php.ini file that is getting used. Check
>>> our the memory settings in that file.
>>>
>>>
>>>
>>>
>>
>> Some general options:
>> max_input_time = 60
>> max_execution_time = 120
>> memory_limit = 128M
>>
>> and the last one I have just noticed (that is why it reports the leak):
>>
>> report_memleaks = On
>>
>> In case I set this to Off it just stops bugging me. But is there a
>> memory leak?
>
> yes.
>
>> And if yes should I report this as a bug ?
>
> if (
>
> 1. report_memleaks is a core php.ini setting (not suhosin) (I don't recall)
> 2. you still get the leak if you disable suhosin extension
> 3. you can create a small reproduction script (seems you have one, but I'd
> check that it's the getopt() call that triggers the leak)
> 4. you can show the mem leak in 5.2.9RC2 and/or php5.3dev
> ) {
> report_a_bug();
> }
>
Syntax error, unexpected T_STRING :(