Re: Callback called exit.

e with an "Out of memory!" message and/or "Callback called exit". Common causes of this -are never-ending loops, deep recursion, or calling an -undefined subroutine. Here's one way to catch the problem: See Perl's -INSTALL document for this item: +are never-ending l

Re: Callback called exit.

of an out of memory error. It prints Out of > >>Memory > >>once, the the process sucks up all available cpu print "Callback > >>called > >>exit." to the log file until it hit's it's 2GB max size. > > > >I'm just guessing

Re: Callback called exit.

Brian Hirt wrote: I've typed up my suggestions to the troubleshooting doc, and incorporated glen's suggestions too. Stas wants me to post to the list to see if there are any comments / corrections. I wasn't sure if I should put a comment in about __DIE__ handlers and their use with evals, it

Re: Callback called exit.

-- src/docs/1.0/guide/troubleshooting.pod 5 May 2004 03:29:38 - 1.28 +++ src/docs/1.0/guide/troubleshooting.pod 6 May 2004 22:40:07 - @@ -589,27 +589,45 @@ If something goes really wrong with your code, Perl may die with an "Out of memory!" message and/or "

Re: Callback called exit.

Glenn wrote: [...] http://perl.apache.org/docs/1.0/guide/troubleshooting.html#Callback_called_exit I've followed that advice and explicitly allocated memory into $^M. I have the following in my mod_perl_startup.pl, which I run from httpd.conf with PerlRequire /path/to/mod_perl_startup.pl If 64K is

Re: Callback called exit.

you use perl's malloc, the advice helps. Doc patches are always welcome here. Please patch against the source pod. http://perl.apache.org/download/docs.html#Download I'd still like to know why mod_perl can get into an infinite loop writtitng "Callback called exit".In p

Re: Callback called exit.

print "Callback called exit." to the log file until it hit's it's 2GB max size. I'm just guessing here, but this is probably because apache is trying to spawn new processes, and they keep dying because there's no memory. Thanks for the response, interesting insight into the h

Re: Callback called exit.

s malloc, the advice helps. I'd still like to know why mod_perl can get into an infinite loop writtitng "Callback called exit".In perl.c, when that happens my_exit_jump(); is called which should presumably exit the process, but somehow that doesn't happen and some s

Re: Callback called exit.

On Wed, 2004-05-05 at 22:11, Brian Hirt wrote: > I've been running across a problem lately where a child process > terminates because of an out of memory error. It prints Out of Memory > once, the the process sucks up all available cpu print "Callback called > exit.&

Re: Callback called exit.

On Wed, May 05, 2004 at 08:11:56PM -0600, Brian Hirt wrote: > I've been running across a problem lately where a child process > terminates because of an out of memory error. It prints Out of Memory > once, the the process sucks up all available cpu print "Callback calle

Callback called exit.

I've been running across a problem lately where a child process terminates because of an out of memory error. It prints Out of Memory once, the the process sucks up all available cpu print "Callback called exit." to the log file until it hit's it's 2GB max