Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:7662 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44143 invoked by uid 1010); 9 Feb 2004 14:07:20 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 44110 invoked by uid 1007); 9 Feb 2004 14:07:19 -0000 To: internals@lists.php.net Date: Mon, 9 Feb 2004 15:07:18 +0100 Message-ID: <20040209150718.7e915311@localhost.localdomain> Organization: Freelancer X-Newsreader: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Posted-By: 213.196.195.213 Subject: unset, memory_limit From: paj@pearfr.org (Pierre-Alain Joye) 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. 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? At least it's a documentation bug as nothing in the manual described this behavior. pierre