I think there should be a solution because Qt someway does it (or are static object used?) to manage object cleanup and things like that... Anyway my component is an application wide memory pool : http://www.qtcentre.org/forum/f-qt-p...age2-6838.html

My problem, as described in this thread, is that I get unexpected crash when using my custom alloc()/dealloc() functions whereas replacing them by qMalloc()/qFree() works well. One could think that my functions are directly responsible for these segfaults but actually it looks trickier than this because my allocator seems to work quite well and segfaults occur in two precise location only : QMutex::lock() and QMutex::unlock() called on wrong pointers from QReadWriteLock::lock() or QreadWriteLock::unlock()...

I thus thought that forcing EVERY SINGLE object to be allocated through the pool would solve this but....