CppCon 2015: Milian Wolff 'Heaptrack: A Heap Memory Profiler for Linux'

preview_player
Показать описание


Lightning Talk


*-----*
*-----*
Рекомендации по теме
Комментарии
Автор

Hello. I have been using heaptracker and I have to say that it is a very nice tool and I am glad that this is available for the people to use.
I have some questions which are bothering me and I can't find the answers to it:

1. How does heaptracker account for memory being allocated by a special, custom allocator?
2. Let's say if we malloc raw memory and then use the placement new operator - that is counted as an allocation - why?
3. Allocated raw memory was part of Allocator's memory pool and when we free/release it, we don't delete it immediately
and it goes back to the free pool to be re-used again.
4. My application which doesn't show any leaks in valgrind memory analysis, shows a tonne of leaks when analysed through
heaptracker.

What is heaptracker's behavior with allocators? How does it detect whether if memory is being actually dynamically allocated OR is being fed from a pre-allocated memory pool ?

gauravarya