(was: mod_perl DSO leaking on restart)
ah ha, right, since i always have PERL_DEBUG=1, perl_destruct_level is
always set to 2. good find! it should always be 2 for dso,
this patch
seems to fix USE_APXS too.
--- src/modules/perl/mod_perl.c 2001/06/14 04:49:08 1.137
+++ src/modules/perl
DM == Doug MacEachern [EMAIL PROTECTED] writes:
DM On 19 Jun 2001, Vivek Khera wrote:
Drat. Not here. I just sucked down the latest mod_perl CVS with this
patch, and I still lose 9M per USR1... Lemme try some tracing to see
what gives here. (FreeBSD 4.3, perl 5.005_03)
DM i mentioned
On Tue, 19 Jun 2001, Christian Gilmore wrote:
Doug,
Will this patch make it into 1.26?
yes.
If so, is there a slated release date for 1.26?
soon-ish. you can always configure: PerlSetEnv PERL_DESTRUCT_LEVEL 2
in the meantime.
On 19 Jun 2001, Vivek Khera wrote:
Drat. Not here. I just sucked down the latest mod_perl CVS with this
patch, and I still lose 9M per USR1... Lemme try some tracing to see
what gives here. (FreeBSD 4.3, perl 5.005_03)
i mentioned earlier in the thread 5.005_03 has leaks. although,
I think I've found the error of my ways.
The reason that it was leaking with a static build was that the
PerlFreshRestart directive was set to 'On'. This resulted in a
leak of a couple of Mb.
The reason that it was leaking with a USE_DSO build was that I didn't set
PERL_DESTRUCT_LEVEL. Once I
ah ha, right, since i always have PERL_DEBUG=1, perl_destruct_level is
always set to 2. good find! it should always be 2 for dso, this patch
seems to fix USE_APXS too.
--- src/modules/perl/mod_perl.c 2001/06/14 04:49:08 1.137
+++ src/modules/perl/mod_perl.c 2001/06/19 01:59:18
@@ -259,8
