I have run into the same issue also both with mod_perl as a DSO module or
compiled staticly. I have tested it using apache-1.3.6 and apache-1.3.12
w/ mod_perl-1.22 and mod_perl-1.21. The memory growth also occurs if I
HUP the server rather than sending USR1. Since the problem only occurs if
mod_perl is loaded (DSO) or staticly loaded, I assume the problem lies in
memory cleanup by modperl. Even if I do nothing other than have mod_perl
installed and HUP the parent, the process will grow at a relatively rapid
rate of over 1MB per HUP instance.
The reason I noticed this is that I cache some relatively static database
information in the parent process by assignment to a package's scoped hash
variables in my startup.pl. I wanted to refresh this cache hourly just in
case changes did happen to occur in the database tables I was caching.
I am curious as to whether there is a better way to go about caching this
data and refreshing it without the problem of watching your apache process
size grow every time you HUP it. Any helpful hints would be appreciated.
The platforms are various Linux kernels ranging from 2.0x to 2.3x. The
majority of which are linux-2.2.10.
<Douglas Leonard>
<[EMAIL PROTECTED]>
On Fri, 7 Apr 2000, Nikki Chumakov wrote:
> mod_perl probaly have memory leakage during rereading configs (e.g. on
> the apachectl graceful)
>
> My system:
>
> RH 6.1,
> linux-2.2.15pre17
> glibc-2.1
>
> apache-1.3.12
> mod_ssl-2.6.2
> russian patches (ftp.lexa.ru/pub/apache-rus/) PL29.4
> mm-1.0.12
> mod_perl-1.22
>
> With mod_perl module enabled in httpd.conf every 'apachectl graceful'
> increase the data memory segment of parent server (and thus the child's
> as well).
>
>
>
>
>
