Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of aganguly01@gmail.com
 designates 64.233.182.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:to:subject:mime-version:content-type;
        b=gCNQgTcgDFgsHEUYv1jRNvZfbBbfY4qZHBHJnoEu1p2n3/foBYZ1eo6Hjn+AK0jjK6/DI2IWxG9Ixg33MgbGGhnfv89WCwHremax27VCH09Kca3AiT2QlavgWtMk5ZpRiqgCNh6pzVT4At/hvP+mfJkBd0YBOhnc+G9+EaOR278=
Message-ID: <2ae67e000803260839v3e1382e6ve46ab1a738286292@mail.gmail.com>
Date: Wed, 26 Mar 2008 21:09:57 +0530
From: "Arnab Ganguly" <aganguly01@gmail.com>
To: modules-dev@httpd.apache.org
Subject: Query on deletion of Request pool
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1251_3103500.1206545997785"

------=_Part_1251_3103500.1206545997785
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All,
I am getting a serious memory issue with my Apache webserver.

Initially I was allocating buffer from by using apr_palloc from the request
pool assuming the allocated memory is going to be released but not sure what
is the problem the memory grows infinitely.

I then tried with own malloc and then added a  clean up function on
apr_pool_cleanup_run.Which on debugging showed the free is being called for
the allocated memory but still the behavior is same.On each request there is
a increase in memory.

Is there any way to release explicitly the memory of the request pool?I
tried with apr_pool_cleanup_register and added a clean up function
internally I was calling apr_pool_destroy(request_rec->pool).For the first
request it worked correctly but on the later there was a crash and restart
on the Apache process.

It seems I may be doing something silly.Any help would be very much
appreciated.BTW my webserver is heavily loaded and it is MPM=Worker Apache
version 2.2.8 and OS is Red-Hat 3.0.

What are the other possibilities where memory leak can looked into.
Looking forward for response.
Thanks
-A

------=_Part_1251_3103500.1206545997785--