Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 72987 invoked from network); 11 May 2007 18:11:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 May 2007 18:11:00 -0000 Received: (qmail 5834 invoked by uid 500); 11 May 2007 18:10:48 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 5820 invoked by uid 500); 11 May 2007 18:10:48 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 5802 invoked by uid 99); 11 May 2007 18:10:48 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2007 11:10:48 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of clint@traveljury.com designates 85.90.230.250 as permitted sender) Received: from [85.90.230.250] (HELO mail.traveljury.com) (85.90.230.250) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2007 11:10:41 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.traveljury.com (Postfix) with ESMTP id A974A1EE5B; Fri, 11 May 2007 19:10:20 +0100 (BST) Received: from mail.traveljury.com ([127.0.0.1]) by localhost (rambaldi.traveljury.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29854-03; Fri, 11 May 2007 19:10:06 +0100 (BST) Received: from [192.168.5.4] (unknown [89.129.44.159]) by mail.traveljury.com (Postfix) with ESMTP id 383E01EA5B; Fri, 11 May 2007 19:10:06 +0100 (BST) Subject: Re: After retrieving data from DB, the memory doesn't seem to befreed up From: Clinton Gormley To: Lionel MARTIN Cc: Clinton Gormley , modperl@perl.apache.org In-Reply-To: References: <66887a3d0705101057v27e48b9s9c7786eeff2dc2fe@mail.gmail.com> <66887a3d0705101450o7d62b529rc20dce49e05f1b96@mail.gmail.com> <66887a3d0705101517m546f5624o6b44bf40ac6ea5d@mail.gmail.com> <66887a3d0705101529o6824fda0kad8d468bc89cdf19@mail.gmail.com> <66887a3d0705102251w1311750fy305be41abd3a6e61@mail.gmail.com> <4644597D.6050502@plusthree.com> <1178904189.4618.35.camel@getafix.traveljury.com> Content-Type: text/plain Date: Fri, 11 May 2007 20:10:05 +0200 Message-Id: <1178907005.4618.38.camel@getafix.traveljury.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at traveljury.com X-Virus-Checked: Checked by ClamAV on apache.org > > > > Obviously, for the second case, I'm assuming that you would do these > > things on a small percentage of your total requests, otherwise killing > > off your child would be a major bottleneck. > > Here, as well, killing a child process under Windows, means killing my whole > Apache server (and so all the serving threads). I thought that $r->child_terminate would work under threaded MPMs as well, but it doesn't. My mistake. clint