perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-François Nadeau <>
Subject RE: PerlRun Memory leak upgrading from 1.99_14 to 2.0.0-RC1
Date Tue, 21 Dec 2004 19:57:47 GMT
Thanks for the quick reply.

I cleaned up my installation and reinstalled.
See attached bug report and

Configured with:
perl Makefile.PL MP_INST_APACHE2=1 MP_AP_PREFIX=/usr/local/apache-2.0.52/ 
make && make install 

The leak persist after reinstall.  

I do not have a sample script at the moment...


-----Original Message-----
From: Stas Bekman [] 
Sent: 21 décembre 2004 11:26
To: Jean-François Nadeau
Subject: Re: PerlRun Memory leak upgrading from 1.99_14 to 2.0.0-RC1

Jean-François Nadeau wrote:
> Hi all,
> I was using mod_perl-1.99_14 under Apache 2.0.49,
> I upgraded to mod_perl-2.0.0-RC1 under Apache 2.0.52.
> Im using RedHat 8.0 / perl 5.8.0 / 3.05
> Apache configuration :
>  SetHandler perl-script
>  PerlResponseHandler ModPerl::PerlRun
>  PerlOptions +ParseHeaders +GlobalRequest
> We only use the PerlRun handler.  
> Since the upgrade,  Apache childs leak (fast).
> Using the old with the current does not leak.
> I attached "mybugreport" 

Please inline those in the future, so one could comment on it in reply.

 > *** The httpd binary was not found

Could you please attach (yes, attach this time :)
I'm trying to figure out why the above happens.

Also what were the exact arguments you've passed to Makefile.PL?

Now back to your problem.

 > *** Packages of interest status:
 > Apache::Request: -
 > CGI            : 3.05
 > LWP            : 5.64, 5.65
 > mod_perl       : 1.9914, 1.9918

That's after you did 'make install' for RC1? how come you have both now?
It now looks that you've installed RC1 with MP_INST_APACHE2=1, whereas
1.99_14 was installed w/o it. So you ended up with a mix of two modperls. 
I suggest you go and nuke any occurences of modperl from your perl tree and
do 'make install' again. The above should report only one mod_perl of the
1.99_ generation.

If the leak still persist, please post a shortest possible script that we
can reproduce the problem with. The best you can do is to prepare a bug
reporting tarball, based on bug-reporting-skeleton-mp2.tar.gz from:

Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker     mod_perl Guide --->

View raw message