On Fri, Jun 12, 2009 at 6:00 AM, Michael Gardner<gardne...@gmail.com> 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 individually. Some kind of per-file memory usage statistics
> from modperl or somesuch.

There are two things you can try.  First, use Apache::Status to see
how much memory is being used by different packages.  If that doesn't
help, add a log handler to your server that prints the difference in
memory used by the current process at the start of the request and the
end of it.  (Capture the size at the start in a fixup handler or
similar.)

- Perrin

Reply via email to