On Mon, 11 Sep 2000, Stas Bekman wrote:
> 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.
I think there are about 3 package variables in total. Its not in them. :-)
> 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.
I'm going to take a more radical approach. A re-write of major portions of
the code to make it easier to track it down. *sigh*...
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org
