Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19809 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 94257 invoked by uid 1010); 29 Oct 2005 06:41:30 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 94242 invoked from network); 29 Oct 2005 06:41:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Oct 2005 06:41:30 -0000 X-Host-Fingerprint: 66.249.82.206 xproxy.gmail.com Linux 2.4/2.6 Received: from ([66.249.82.206:25226] helo=xproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 79/67-01249-99913634 for ; Sat, 29 Oct 2005 02:41:29 -0400 Received: by xproxy.gmail.com with SMTP id t13so415217wxc for ; Fri, 28 Oct 2005 23:41:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=j6vw+b/Le/NFo3ZUomwAgNR/B6uMCU4zHR3oeVoR4c0Zq7TEYFnTR6UEFjgw7/aMJ7nEDn27aWx/ElUBul+eJ4WcNPXabg40DRCdcnzlPVtgrpHERdG6pbUBRTtHMP5ovYhy2Gfvtahb0VjFcop+7rYeuU0z9XXnybjLa56w+DA= Received: by 10.65.188.14 with SMTP id q14mr656355qbp; Fri, 28 Oct 2005 23:41:25 -0700 (PDT) Received: by 10.64.183.1 with HTTP; Fri, 28 Oct 2005 23:41:25 -0700 (PDT) Message-ID: <4e36d31d0510282341r2de4d2edta85bb2611897c7b0@mail.gmail.com> Date: Fri, 28 Oct 2005 23:41:25 -0700 To: Andi Gutmans Cc: internals@lists.php.net In-Reply-To: <6.2.3.4.2.20051028221433.02d081d0@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4E.0D.57990.B3A72634@pb1.pair.com> <6.2.3.4.2.20051028132228.0a164030@localhost> <4e36d31d0510281850q625316ccx1dd4a61ba59b23f8@mail.gmail.com> <6.2.3.4.2.20051028221433.02d081d0@localhost> Subject: Re: [PHP-DEV] 1.5Gb PHP process, lots of swap From: buddhahead@gmail.com (Sebastian) Something like the variables produced by perl's my() operator so that a variable is lexically scoped along with block-level scoping could help earlier detection of when it's possible to release a variable. This wouldn't solve leaks, but it might help prevent some On 10/28/05, Andi Gutmans wrote: > What do you mean? > > At 06:50 PM 10/28/2005, Sebastian wrote: > >Lexical variables would be nice. > > > >On 10/28/05, Andi Gutmans wrote: > > > Hi Cristiano, > > > > > > Alex sent a patch to the list a while ago which forces the memory > > > allocator to return memory to the system. However, in your case, I > > > think you might be just having PHP variables "leaking". Can you try > > > and identify where this info is sitting and try and unset it? It's > > > important to dig deeper and/or reproduce in order to understand. > > > > > > > > > Andi > > > > > > At 12:21 PM 10/28/2005, Cristiano Duarte wrote: > > > >Is there any way to force a PHP CLI application to free the memory i= t took > > > >from the system ? I mean, is there any PHP userland or PHP internal > > > >functional call that could *really* free 'the memory allocated by a > > > >variable' or 'the memory allocated but currently not used and waitin= g for > > > >the script end to be freed' ? > > > > > > > >Regards, > > > > > > > >Cristiano Duarte > > > > > > > >-- > > > >PHP Internals - PHP Runtime Development Mailing List > > > >To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > -- > > > PHP Internals - PHP Runtime Development Mailing List > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > >-- > > > > > > > >------------- > >buddhahead@gmail.com > > -- ------------- buddhahead@gmail.com