Robert Landrum wrote:
>
> I have some very large httpd processes (35 MB) running our
> application software. Every so often, one of the processes will grow
> infinitly large, consuming all available system resources. After 300
> seconds the process dies (as specified in the config file), and the
> system usually returns to normal. Is there any way to determine what
> is eating up all the memory? I need to pinpoint this to a particular
> module. I've tried coredumping during the incident, but gdb has yet
> to tell me anything useful.
First, BSD::Resource can save you from these. It will do hard limits on
memory and CPU consumption. Second, you may be bale to register a
handler for a signal that will generate a stack trace. Look at
Devel::StackTrace (I think) for how to do it.
- Perrin
