which allocate memory before we can call cass_alloc_set_functions(). During process exit, those objects use our custom free() instead of std::free() to match std::malloc() that allocated the memory.
My current work around is to ignore your calls to my custom free() during process shutdown.
We use the mspace feature of Doug Lea's malloc to have multiple heaps. Allocating in one heap and freeing in another heap is never a good idea.
The C++ driver has these objects
const Address Address::EMPTY_KEY(String(), 0);
const Address Address::DELETED_KEY(String(), 1);
which allocate memory before we can call cass_alloc_set_functions().
During process exit, those objects use our custom free() instead of std::free()
to match std::malloc() that allocated the memory.
My current work around is to ignore your calls to my custom free() during process shutdown.
We use the mspace feature of Doug Lea's malloc to have multiple heaps.
Allocating in one heap and freeing in another heap is never a good idea.