Re: Memory Leaks in mod_perl
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 section (though this may be because it's implicitly loaded by having a 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/ bjbDon't try to drive me crazy... \_/...I'm close enough to walk.
Re: Memory Leaks in mod_perl
On Thu, Nov 04, 1999 at 12:32:07PM +, Ben Bell wrote: > 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. It's DSO related for sure, I've built a static 1.3.9/1.21 here and it doesn't do this at all. I've hacked the Debian package to build with static mod_perl in the Apache binary, source and binary packages are at: http://elgin.plcom.on.ca/debian/dists/unstable/main/ Or put this in your /etc/apt/sources.list and "apt-get install apache-perl": deb http://elgin.plcom.on.ca/debian unstable main (note: this server may be up and down for a bit, it's also the development machine for my project at work that uses mod_perl...) These aren't official packages, of course. Hopefully the memory leakage on DSO problem can be resolved before we release potato, it is a rather severe bug IMHO.
Memory Leaks in mod_perl
Hi, 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 (though without any PerlRequire directives or PerlHandlers or sections it still leaks about 64k of memory on each SIGHUP) 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) Apache/1.3.9, mod_perl 1.21, Debian potato/alpha (perl 5.005_03) Apache/1.3.9+mod_ssl/2.4.2, mod_perl 1.21, Debian potato/i386 I have seen it with PerlFreshRestart both on and off (I should note that I didn't notice it as much on Red Hat because Red Hat (grumble) don't include apachectl in their packages and their init.d script does a full shutdown and restart) 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)
