DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29690>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29690 allocator_free() crashes because of NULL-Pointer inside SSL_smart_shutdown() ------- Additional Comments From [EMAIL PROTECTED] 2004-06-20 00:40 ------- I am sorry - it's me again ;-) But this problem doesn't want to let me go... In apr_pool_clear(), the following is done: 1. Destroy the subpools - *first* 2. Run cleanups 3. Free subprocesses Could it be that the cleanups do something wrong when they allocate memory (and the SSL shutdown *does*!!) and the subpools are already destroyed? When I change this to: 1. Run cleanups 2. Free subprocesses 3. Destroy the subpools - *last* Everything works fine (w/o my previous quiet_shutdown workaround!). Question: Is this ok, or does it maybe produce memory leaks? I admit that I still don't fully understand the pool concept :-) BTW: The same questions apply to the apr_pool_destroy() function which does the same three steps for the sub-pools. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
