Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19458 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57561 invoked by uid 1010); 6 Oct 2005 18:44:09 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 57546 invoked from network); 6 Oct 2005 18:44:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Oct 2005 18:44:09 -0000 X-Host-Fingerprint: 195.197.172.115 gw01.mail.saunalahti.fi Linux 2.4/2.6 Received: from ([195.197.172.115:39018] helo=gw01.mail.saunalahti.fi) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 1D/BD-54476-87075434 for ; Thu, 06 Oct 2005 14:44:08 -0400 Received: from nest.netphobia.fi (YZDCXXXI.dsl.saunalahti.fi [85.76.35.232]) by gw01.mail.saunalahti.fi (Postfix) with ESMTP id 3A28FF15FD; Thu, 6 Oct 2005 21:44:02 +0300 (EEST) Received: from nest.netphobia.fi (nest.netphobia.fi [127.0.0.1]) by nest.netphobia.fi (8.13.1/8.13.1) with ESMTP id j96Ii4WV027929; Thu, 6 Oct 2005 21:44:04 +0300 Received: from localhost (jani@localhost) by nest.netphobia.fi (8.13.1/8.13.1/Submit) with ESMTP id j96Ii3qC027926; Thu, 6 Oct 2005 21:44:04 +0300 X-Authentication-Warning: nest.netphobia.fi: jani owned process doing -bs Date: Thu, 6 Oct 2005 21:44:03 +0300 (EEST) Reply-To: Jani Taskinen To: "J. Allen Dove" cc: Sara Golemon , internals@lists.php.net In-Reply-To: <4E0C5C8E5F8C994F90134920DD66E93F01129374@pearl.hq.booyahnetworks.com> Message-ID: References: <4E0C5C8E5F8C994F90134920DD66E93F01129374@pearl.hq.booyahnetworks.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: RE: [PHP-DEV] Re: CLI in PHP6 From: sniper@iki.fi (Jani Taskinen) There was some mail about the memory handling some time ago on this list..something about making it better in these cases.. Try search the archives for this. (I can't find it right now) IIRC, there even was a patch.. --Jani On Thu, 6 Oct 2005, J. Allen Dove wrote: > Unset() != free() is the bummer in the CLI env. :-( Def could use that > to help shape the performance contour in a daemon env since the > "request" never ends unless you self-terminate. Even then it can be > tricky to get that lifetime right if your loads change, etc. > > -- AD > >> "leak", which honestly surprised me. We even explicitly unset the vars >> but that doesn't guarantee the GC kicks off for them near-time? >> >> unset() != free(). The memory allocated is still freed during >> the request shutdown (where GC actually kicks in). >> >> As a total aside, and being a paranoid C++ guy, I would love a "free" >> method that I could call that frees what I tell it to exactly when I >> tell it to... :-) >> >> I think someone requested this before but it was shut down for >> some reason..can't remember what it was again. > > -- Give me your money at @ Donating money may make me happier and friendlier for a limited period! Death to all 4 letter abbreviations starting with P!