On Wed, 2008-09-03 at 17:08 +0100, Ian Gardner wrote: > Each thread calls apr_thread_mutex_destroy on a different mutex, but in > the same pool.
> Looking naively at apr_pool_cleanup_kill it would appear to be modifying > pool state variables without any sort of concurrency protection which > could explain the problem. Pools are explicitly thread unsafe, so if you you are doing something to the same pool from two different threads, you must synchronise using your own mutex. -- Bojan
