On 5/12/05, Joe Schaefer <[EMAIL PROTECTED]> wrote: > Without this patch, the new apr_pool_join stuff in apr's trunk > segfaults all over the place.
Why? Is worker MPM doing something wrong (creating standalone pool in that manner), or does APR need some help? > Index: server/mpm/worker/worker.c > apr_allocator_create(&allocator); > apr_allocator_max_free_set(allocator, ap_max_mem_free); > - apr_pool_create_ex(&ptrans, NULL, NULL, allocator); > + apr_pool_create_ex(&ptrans, pconf, NULL, allocator); Isn't this on the listener thread? Do we need to be mucking with the pconf pool on non-main thread? Sounds dangerous (non-thread-safe).
