Hmmm. We're using Apache 1.3.12, perl 5.6.0 and
mod_perl 1.24. There aren't any huge leaks that
we can't attribute to our custom C++ module.
Maybe try upgrading mod_perl to 1.24?
Otherwise, you'll have to do what we did.
Get a memory checking tool (boundschecker for us)
and spend a few weeks grubbing through the
code. yechh.
-harshy
> From: Son Chang [mailto:[EMAIL PROTECTED]]
>
> I saw this fix in one of the mailing list archives and tried
> it but I'm still
> getting the memory leak.
>
> -son
>
> Quoting Harshy Wanigasekara <[EMAIL PROTECTED]>:
>
> > Son Chang wrote:
> > >Hi,
> > >
> > >I'm experiencing a memory leak with Apache 1.3.14 with
> mod_perl 1.23
> > and
> > >perl5.6.0 on Windows NT4.0 and Windows2000.
> > >I've been running some test with a very simple ModPerl
> handler which
> > just
> > >outputs an HTML page with hello world in it. Also, I made sure to
> > undef
> > >all
> > >variables that I use.
> > >In general, the child processes grow with each request.
> > >Also, if I set MaxRequestsPerChild to 20 so the child
> process dies and
> > >restarts after every 20 request, this fixes the problem
> for the child
> > >processes. However, with this configuration, there's a memory leak
> > >problem with the parent process. After the child process dies and
> > >restarts, the parent process grows in size. This happens
> every time
> > the
> > >child process dies and restarts.
> > >So with either configuration, I have a memory leak problem.
> > >What can I do to fix this problem?
> > >
> > >-son
> >
> > Heh, I just unsubscribed from the mailing list,
> > almost missed your question.
> >
> > We ran into the exact same problem here.
> >
> > Try:
> >
> >
> http://forum.swarthmore.edu/epigone/modperl/groxbloiglim/03AB3
CB11CBED3118A4
> F009027B0C2B16B71A4@HAPPY
>
> Our fix stops the child process growing, but not the parent.
>
> -harshy
>
> --
> Harshy Wanigasekara, Software guy, Omneon Video Networks.
>
