On Mon, 11 Sep 2000, Matt Sergeant wrote:
> On Mon, 11 Sep 2000, Stas Bekman wrote:
>
> > I was thinking about going thru the symbol table and dumping all the
> > variables. And run diff between the dumps of the two requests. Be careful
> > though that Devel::Peek doesn't show a complete dump for the whole
> > structure, and I couldn't find the interface for changing the deepness of
> > datastructure traversal. I think Doug has patched Apache::Peek to make
> > this configurable.
> >
> > Do you think it still won't work?
>
> Yes. Because this only seems to give you access to package variables, not
> trapped lexicals or anything in closures.
Well, you don't know where the leakage is. May be the problem *is* in the
package variables... At least if you prove that it's not, you narrow your
search path.
What I'd do is taking the module that prints the Stack trace and patch it
to print memory foot print after each trace line with GTop or else, and
then just grep for the first place where the memory bumps up and find the
offending code. Of course you have to take into account Frank's reply.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://jazzvalley.com
http://singlesheaven.com http://perlmonth.com perl.org apache.org
