Re: Finding memory leaks

Check out Devel::Leak. That might help you track this problem down. It helps if you have Perl compiled with -DDEBUGGING.

I also have to say that, from what I read from your post, you mentioned that you have reduced your test case down to something that doesn't produce memory leaks. In that case, keep adding things back until you get the memory leak. A test case which doesn't reproduce the problem isn't terribly useful. Also, since you're using Solaris, you might find this article interesting. It talks about the large number of "leaks" in 5.6.1 on Solaris - though there is some disagreement over what constitutes a leak.

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

Comment on Re: Finding memory leaks

Replies are listed 'Best First'.
Re: Re: Finding memory leaks by steves (Curate) on Apr 24, 2002 at 17:28 UTC
I was unclear. My small loop does produce the leak, so I've narrowed it down to a handful of packages used under that loop. And I have one include path of older versions of those that doesn't leak. That's what's frustrating: I've basically done a line by line comparison between the two package sets and haven't found anything. What this means, of course, is that it will turn out to be something embarrassingly obvious and stupid. 8-)	[reply]

Replies are listed 'Best First'.

Re: Re: Finding memory leaks
by steves (Curate) on Apr 24, 2002 at 17:28 UTC

I was unclear. My small loop does produce the leak, so I've narrowed it down to a handful of packages used under that loop. And I have one include path of older versions of those that doesn't leak. That's what's frustrating: I've basically done a line by line comparison between the two package sets and haven't found anything. What this means, of course, is that it will turn out to be something embarrassingly obvious and stupid. 8-)

[reply]