Memory leak in MemPool

[TarakanoLov]

Hi, I'm reading https://github.com/PacktPublishing/Building-Low-Latency-Applications-with-CPP/blob/main/Chapter4/mem_pool.h and I can't understand why the destructor in deallocate is not called, it turns out after creation std::string will leak memory in place of the old std::string

[linoxoidunix]

it is mustn't a big problem for you. you can easy use other Memory impl here. For example this project
https://github.com/cacay/MemoryPool

Hi, I'm reading https://github.com/PacktPublishing/Building-Low-Latency-Applications-with-CPP/blob/main/Chapter4/mem_pool.h and I can't understand why the destructor in deallocate is not called, it turns out after creation std::string will leak memory in place of the old std::string

[XiaoTonyLuo]

I think the deallocation function doesn't destroy the objects in memory pool since the allocation function doesn't allocate memory for the input objects. All the memory was pre-allocated in memory pool's construction, and the allocation function just construct the given objects on existing memory.