Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:7665
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Mon, 9 Feb 2004 15:27:52 +0100
To: internals@lists.php.net
Message-ID: <20040209152752.749cbfff@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.58.0402091513410.2605@localhost>
References: <20040209150718.7e915311@localhost.localdomain>
	<Pine.LNX.4.58.0402091513410.2605@localhost>
Organization: Freelancer
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] unset, memory_limit
From: paj@pearfr.org (Pierre-Alain Joye)

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