Thanks for the tips. For the record, it turned out that the "leak"
wasn't really a leak at all: we have a *large* directory structure in
which each directory was using as its index file a symlink to the same
perl file (which in turn used the REQUEST_URI to figure out what content
to serve). Apparen
On Fri, Jun 12, 2009 at 6:00 AM, Michael Gardner wrote:
> The problem is that there are a lot of perl files to check out, and I
> don't know which one has the leak. What I'm asking is whether there's a
> way to figure out *which file* is leaking memory, without having to test
> each file individual
Michael Gardner wrote:
William T wrote:
There are some leak analysis modules that may help (Devel::Leak I
think). I've tried using them in the past, but they haven't worked
well for me for various reasons. I found commenting out early branch
points allowed me (most of the time) to narrow down
William T wrote:
> There are some leak analysis modules that may help (Devel::Leak I
> think). I've tried using them in the past, but they haven't worked
> well for me for various reasons. I found commenting out early branch
> points allowed me (most of the time) to narrow down where the leak was
I'm working with some old perl code that was previously running under
modperl 1.x, but was recently updated for 2.x. There is a fairly severe
memory leak somewhere in this code, but I'm having a hell of a time
tracking it down.
The problem is that I don't know which of our many perl files is causi
