DO NOT REPLY [Bug 20064] - child memory pool not cleaned up after child terminates

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20064>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20064

child memory pool not cleaned up after child terminates





------- Additional Comments From trawick@apache.org  2003-05-20 17:46 -------
Are you really using perchild MPM as specified as the component for this PR? 
You don't mention the OS.

>The memory pool handed to the child_init hook is (apparently) 
>supposed to be freed up at/after the termination of the child 
>process.

yes

>In my testing, the memory pool is not freed up at this time 
>but at the shutdown of the main httpd process.

the memory pool does not exist in the main httpd process

when the main process is shutdown, all child processes will exit and cleanups
registered against pchild will be run then in the child processes

>I'm unsure why child_exit was removed in 2.0

it was removed because it isn't necessary

there are other potential hooks (e.g., post connection) that aren't implemented
either...  the module author is expected to use a cleanup registered against the
right pool

Can you show us how to recreate the problem?  Can you trim down your module to a
trivial piece of code that has a child init hook that registers a cleanup
against the code passed in, and does something obvious (writes a message to a
file??) to indicate whether or not the cleanup was run?

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org