Thank you, Nick, for your answer, > > So would this result in a memory leak? (if this happens often!) > > Potentially yes, unless you can do an exhaustive analysis of all > possible processing paths. > > The fix for that is to register a free as a pool cleanup > immediately after the malloc/realloc. See mod_proxy_html > for an example.
Thanks for this suggestion. If I do not find out what is causing the apache childs to grow in memory usage, I will try this to be sure it's not my memory allocations. Greetings. -- Christoph Gröver, gro...@sitepark.com
