Finding memory leaks in C++ with heaptrack

This page cannot be shown here. You can still read it on the original site — the toolbar below keeps your place in the directory.

While scouring the internet for ways to track memory usage of processes, I found a lot of resources on valgrind(+massif). While valgrind is useful, it slows down your program significantly. This is particularly problematic when you have a memory leak that takes a long time to occur or balloon into a large amount. In my experience, heaptrack runs much faster 1 . Some approaches modify calls to new…

Read on /blog/finding-memory-leaks-in-cpp-with-heaptrack/ ↗