Re: unset, memory_limit

From: Date: Mon, 09 Feb 2004 14:27:52 +0000
Subject: Re: unset, memory_limit
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-7665@lists.php.net to get a copy of this message
On Mon, 9 Feb 2004 15:14:46 +0100 (CET) Derick Rethans <derick@php.net> wrote: > > 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. Not sure if I got the idea ;). If compiled with m_l, unset frees the var and the mem. If not, the mem is still allocated. Btw I was wrong, memory_limit set to -1 works too. > > Or is there any "performance" issues there? > > I think it's a default unix thing actually :) Hmm, I'm missing something here. If I understand this is due to my poor linux if I can't free the mem in my php script? :) but only if I use the memory_limit option. pierre

« previous php.internals (#7665) next »