Re: avoiding child death by size limit

2009-12-11 Thread William T
On Thu, Dec 10, 2009 at 11:28 AM, E R pc88m...@gmail.com wrote: Hi, I have a problem where a mod_perl handler will allocate a lot of memory when processing a request, and this causes Apache to kill the child due to exceeding the configure child size limit. Are there any special techniques

bytes malloc-ed less bytes free-ed

2009-12-11 Thread E R
as kind of a followup to my last question... is there a way to determine this quantity: the amount of memory malloc-ed minus the amount of memory free-ed? It seems that this would be easy for malloc()/free() to keep track of. I would like to compare that value with the process size to get an

Re: avoiding child death by size limit

2009-12-11 Thread André Warnier
E R wrote: Hi, I have a problem where a mod_perl handler will allocate a lot of memory when processing a request, and this causes Apache to kill the child due to exceeding the configure child size limit. Chances are that a child does not exceed this memory right away, at the first request.

Re: avoiding child death by size limit

2009-12-11 Thread Perrin Harkins
On Fri, Dec 11, 2009 at 11:37 AM, William T dietbud...@gmail.com wrote: You can make sure the variables that the memory was malloc'd for have gone out of scope, and there are not trailing references to them. Perl will then reuse that memory. It will keep the memory allocated to the

Re: avoiding child death by size limit

2009-12-11 Thread André Warnier
Perrin Harkins wrote: On Fri, Dec 11, 2009 at 11:37 AM, William T dietbud...@gmail.com wrote: You can make sure the variables that the memory was malloc'd for have gone out of scope, and there are not trailing references to them. Perl will then reuse that memory. It will keep the memory

Re: avoiding child death by size limit

2009-12-11 Thread Perrin Harkins
On Fri, Dec 11, 2009 at 5:56 PM, André Warnier a...@ice-sa.com wrote: When you say It (perl) will keep the memory, do you mean that - the perl interpreter embedded in this Apache child will keep the memory (and not return it to the OS), but will re-use it if possible for other variable

[error] Software caused connection abort at

2009-12-11 Thread discobeta
Dear all, Recently i've been noticing an error on the apache error log that states:[error] Software caused connection abort at [script path] line [line number]. Subsequently, i've been noticing another error, :Apache IO flush: (103) Software caused connection abort at -e line 0 Always fails

Re: [error] Software caused connection abort at

2009-12-11 Thread Kurt Hansen
discobeta wrote: Dear all, Recently i've been noticing an error on the apache error log that states:[error] Software caused connection abort at [script path] line [line number]. Subsequently, i've been noticing another error, :Apache IO flush: (103) Software caused connection abort at -e