On 15 Apr 2002, Jeff Trawick wrote: > But if I make a change to worker to get rid of the > apr_bucket_alloc_destroy() I can't reproduce the problem. > > What is happening is that the thread's pool is getting cleaned up > before the thread goes away (baaaad) since the thread pool is a > subpool of pchild and pchild can go away before the thread with a > graceful restart.
Wow, that's funky. Sheesh. > At the moment, the right fix seems to be for a thread pool to be > stand-alone, but I'd guess there are at least 10 reasons I can't think > of for why that is a stupid idea :) I'll have to think on this for a while. My question is: why is pchild getting cleaned up so early? > Also, it would be nice if the apr_bucket_alloc code followed the usual > pattern for destroy/cleanup (see apr_file_close() for an example, > where we call apr_pool_cleanup_run()). It works as-is, but you have > to stare at it for a while :) Done. :) -------------------------------------------------------------- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA
