I've written a module which I believe to be thread-safe but appears to be
doing something which I have put down to a lack of thread safety in pool
management (somewhere).
Before I tear my hair out here, my module is running with apache 2.2.22
and mpm-prefork on Ubuntu. Do the thread primatives
On 2013-06-11 21:20, Alex Bligh wrote:
I've written a module which I believe to be thread-safe but appears to be
doing something which I have put down to a lack of thread safety in pool
management (somewhere).
Before I tear my hair out here, my module is running with apache 2.2.22
and
Sorin,
On 11 Jun 2013, at 21:57, Sorin Manolache wrote:
The threadallocatormutex is created from a child of the request pool. The
request pool and its child-pools are destroyed when the request terminates.
Do you use the threadpool/threadallocator/threadallocatormutex afterwards?
Nope.
On 11 Jun 2013, at 23:06, Sorin Manolache wrote:
I'm sorry, I ran out of ideas. I suppose that the operations of the two
threads on the bucket brigade are protected by mutexes...
Yep. I create my own output bucket brigade too. I *presume* this uses the
allocator mutex to manipulate the
