heaptrack

I've personally found heaptrack[1] pretty good for this task, very straightforward to use and the info is detailed enough. Though, it'll only tell you where they are happening (e.j. allocation rate for Box::new), but not exactly what type they are given that info isn't available at runtime. Usually that kind of thing would be reserved to GC-based languages where they keep track of counts for each object. 1: https://github.com/kde/heaptrack

If we are talking replacing the libc allocator, then something like heaptrack is worth mentioning. https://github.com/KDE/heaptrack

https://valgrind.org/docs/manual/ms-manual.html https://github.com/KDE/heaptrack https://elinux.org/Electric_Fence https://github.com/google/sanitizers/wiki

> memory leaks. It's surprisingly hard to find an easy to use memory leak detection tool. I can vouch for heaptrack[1] nowadays, although it's pretty much Linux only. It's under the umbrella of KDE, but a heaptrack trace only requires a CLI app, and there is a nice Qt viewer to analyse the memory consumption. It tracks the memory utilization at the level of malloc'd/free'd bytes. It's fine if your memory leak or other memory utilization problem is on this level. Recently I dealt with an issue, where increasing memory utilization was caused by fragmentation within the allocator. This didn't show up in heaptrack as an increasing memory utilization, but heaptrack still pointed out where most of the temporary allocations happened, leading to the culprit of the fragmentation. [1] https://github.com/KDE/heaptrack

Could you compare/contrast its functionality to https://github.com/KDE/heaptrack ?

No, but you can use the docker script I use to generate the AppImage as a basis: https://github.com/KDE/heaptrack/blob/master/tools/Dockerfil...

In case someone is looking for the equivalent on Linux and Mac, there is HeapTrack https://github.com/KDE/heaptrack edit: typo