Re: Re: memory allocation and de-allocation

From: Date: Wed, 13 Mar 2002 12:42:19 +0000
Subject: Re: Re: memory allocation and de-allocation
References: 1 2 3 4 5 6 7 8 9 10 11  Groups: php.gtk.dev 
Request: Send a blank email to php-gtk-dev+get-369@lists.php.net to get a copy of this message
mmm yes, just been off playing with an as/400 (shudder), mind blank.. I don't quite understand why php-dev, if php itself is deallocating the stuff when I disable the fast cache and when I unset a gui widget it doesn't surely then it relates to php-gtk's code not calling the free? sorry if that sounds newbieish, i need way more coffee today brett > heh, I meant php-dev@ ... not php-gtk-dev ;-) > > On Wed, Mar 13, 2002 at 02:34:41PM +0200, Brett Geer wrote : > > Hi All, > > > > shifting this from the php-gtk list to the dev list, basically what I've got > > is allocating variables and then using unset to free them doesn't do anything, > > memory still remains allocated, setting the fast cache off gets this working > > however unset'ing gui widgets doesn't do anything. > > > > PHP 4.1.1 with the php-gtk at 0.5, I'm loading about 26k rows into a clist and > > then when I've got what I need out of it I unset it and the memory remains > > allocated... > > > > This applies to the other widgets I use aswell > > > > brett > > > > > Yes, my cgi module is still intact, thats on a production server, the commandline > > > version did see a performance hit when I was allocating the array without the fast > > > cache enabled, though normally I'd not go do something silly like roll 26k > > > records > > > into an array I might have to do that sooner or later. > > > > > > I was trying some work based on your intro doc which is what got me into the idea of > > > the php-gtk interface. Nice examples you've got up, very helpfull. > > > > > > Lemme subscribe to the php-dev list and raise this issue > > > > > > brett > > > > > > > > > > > > > > > > > > > On Wed, Mar 13, 2002 at 12:41:02PM +0200, Brett Geer wrote : > > > > > yes indeed, php 4.1.1 > > > > > > > > > > this code idea: > > > > > > > > > > #allocate > > > > > for ($vloop = 0; $vloop <= 200000; $vloop++) > > > > > { > > > > > $varr [$vloop] = "Some arb string to grab some ram..."; > > > > > } > > > > > > > > > > #deallocate > > > > > unset ($varr); > > > > > > > > > > This works quite fine, however an unset on a gui widget does do this, I > > > > > have > > > > > recompiled php-gtk 0.5.0. > > > > > > > > Possible it just not implemented... > > > > > > > > Anyway .. if this is true for memory allocation, can we say > > > > something about performance loss if you change this > > > > behaviour? > > > > > > > > Why I'm asking is simply exmplained: php in apache and php on > > > > command line are two different worlds. On apache side, it may > > > > be a good idea not to release memory. However, from my point > > > > of view it makes very much sense for the CLI version of PHP > > > > and maybe we should raise this to php-dev@ to discuss certain > > > > things about this aspect there. > > > > > > > > - Markus > > > > > > > > -- > > > > Please always Cc to me when replying to me on the lists. > > > > GnuPG Key: > > > > http://guru.josefine.at/~mfischer/C2272BD0.asc > > > > > > > > -- > > PHP-GTK Development Mailing List (http://gtk.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > -- > Please always Cc to me when replying to me on the lists. > GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc >

« previous php.gtk.dev (#369) next »