> -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
On Sun, 10 Sep 2000, Matt Sergeant wrote:
> For 2 days solid now I've been trying to track down a very bizarre memory
> leak in AxKit.
>
> I've checked everything I can think of - all circular references are now
> gone, all closures clean up carefully after themselves, and I've reduced
> the usa
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
> > >
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 fo
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 inte
On Sun, 10 Sep 2000, Matt Sergeant wrote:
> On Sun, 10 Sep 2000, Stas Bekman wrote:
>
> > On Sun, 10 Sep 2000, Matt Sergeant wrote:
> >
> > > For 2 days solid now I've been trying to track down a very bizarre memory
> > > leak in AxKit.
> > >
> > > I've checked everything I can think of - all
On Sun, 10 Sep 2000, Stas Bekman wrote:
> On Sun, 10 Sep 2000, Matt Sergeant wrote:
>
> > For 2 days solid now I've been trying to track down a very bizarre memory
> > leak in AxKit.
> >
> > I've checked everything I can think of - all circular references are now
> > gone, all closures clean up
Matt Sergeant <[EMAIL PROTECTED]> writes:
> Now to the wierd bit. I could track this down if it wasn't for this:
>
> The memory leak starts after the Nth hit, usually around 35. This is
> running under httpd -X.
>
> So it goes along very happily for 35 hits - memory usage is rock solid
> stable.
Matt Sergeant wrote:
> Can anyone give me _any_ help in figuring out where this might be coming
> from?
When I'm working on problems like this, there are two basic things I
try. They're not rocket science, but they usually work. The first is
removing sections of code until the leak goes away.
On Sun, 10 Sep 2000, Matt Sergeant wrote:
> For 2 days solid now I've been trying to track down a very bizarre memory
> leak in AxKit.
>
> I've checked everything I can think of - all circular references are now
> gone, all closures clean up carefully after themselves, and I've reduced
> the usa
For 2 days solid now I've been trying to track down a very bizarre memory
leak in AxKit.
I've checked everything I can think of - all circular references are now
gone, all closures clean up carefully after themselves, and I've reduced
the usage of some external modules. But still the processes gr
11 matches
Mail list logo