Re: unset, memory_limit
| From: | Derick Rethans | Date: | Mon, 09 Feb 2004 14:14:46 +0000 |
| Subject: | Re: unset, memory_limit | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-7663@lists.php.net to get a copy of this message | ||
On Mon, 9 Feb 2004, Pierre-Alain Joye wrote:
> Hello,
>
> While reading the bugs reports I came up with something I did not
> expect with the bug 27714. Maybe I have had too much ram in the past
> years ;)
>
> So this is bug is bogus, and this is the expected behavior. Unset
> (or set the var null) frees the memory only if memory_limit is enabled
> and not equal to -1 (unlimited) for both php5 and php4.
memory_limit has nothing to with the real memory usage. m_l only is
internal emalloc'ed and efree'd memory.
> Why? That's sound a bit silly to me, as that makes the related
> functions useless and does not allow anyone to free a huge variable
> when he does not need it anymore. My main problem is when I use CLI or
> gtk scripts.
>
> Or is there any "performance" issues there?
I think it's a default unix thing actually :)
Derick