On Wed, Nov 03, 1999 at 10:40:08PM -0500, David Huggins-Daines wrote:
> I have more or less the same problem as Ben here. mod_perl appears to leak
> memory on SIGHUP proportionately to the number of extra Perl modules loaded
> into the interpreter
I think to some extent individual modules are to blame (though again - this
might be something in the Apache core that they use).
When I did some checking I found that PerlModule Apache didn't seem to leak
any more memory than just having a <perl> section (though this may be
because it's implicitly loaded by having a <Perl> section - anyone confirm
this?) Apache::Status on the other hand leaked around 936K. Apache::DBI (not
PerlSections as I stated in my last post) leaks 404K, though 360K of this
seems to be DBI itself.
It seems to be the native code Perl Modules that cause the most trouble.
Maybe a short term solution to this would be to allow a directive which
destroys the Perl interpreter on restarts.
> I have experienced this with:
> Apache/1.3.6, mod_perl 1.21, Red Hat 5.2/i386 (perl 5.004_05 and 5.005_03)
Well I guess it's not something bizarre about the way tha Debian compiled
it then.
> I have not been able to check earlier versions of mod_perl because I can't
> seem to find them on CPAN :)
>
> Please also note Debian bug reports #34947 and #41946.
> (http://bugs.debian.org/34947, http://bugs.debian.org/41946)
Bug 34947 might be a different problem. But if it is, the poster stated
that statically linked 1.3.3/1.16_02 worked well for him. I'll see if
I can track down some earlier versions and build them like this.
Ben
--
+-----Ben Bell - "A song, a perl script and the occasional silly sig.-----+
/// email: [EMAIL PROTECTED] www: http://www.deus.net/~bjb/
bjb Don't try to drive me crazy...
\_/ ...I'm close enough to walk.
