> -----Original Message-----
> From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 11, 2000 2:54 PM
> To: Matt Sergeant
> Cc: [EMAIL PROTECTED]
> Subject: Re: Memory leak hell...
>
>
[snip]
> look for xsubs in those modules you're using that are calling
> new{SV,AV,HV,RV} or SvREFCNT_inc(). sounds like botched refcnting or
> failure to mortalize a new*V.
> actually, my first guess is Apache::ModuleConfig->get, if you don't
> explicitly pass __PACKAGE__ as the last argument, perl_eval_pv() is
> called, which has a leak plugged in perl-current:
>
> [ 6201] By: gsar on
> 2000/06/06 00:42:59
> Log: Perl_eval_pv() leaks 4 bytes every time it is
> called because it
> does a PUSHMARK that's never ever POPMARKed; in
> general, only
> Perl_call_[sp]v() need a PUSHMARK for incoming arguments;
> Perl_eval_[sp]v() don't because they don't take
> any incoming
> arguments (this leak has been around since the
> original version
> of perl_eval_pv() in 5.003_97e)
> Branch: perl
> ! perl.c
>
> so first try changing:
> Apache::ModuleConfig->get($r)
> to
> Apache::ModuleConfig->get($r, __PACKAGE__)
that's a good bit of info to know - thanks...
--Geoff
>
