Simply put, is the first preload on the Tcmalloc, the daily use of no problem, when the feeling of problems, gdb attach, and then execute call heapprofilerstart ("xxx"), over a period of time, then execute call Heapprofi Lerstop, output the corresponding profile file, and then detach out the process
Here are some of the unfinished link
Https://gperftools.github.io/gperftools/heapprofile.html
Https://linux.cn/article-9588-1.html
Https://unix.stackexchange.com/questions/36450/how-can-i-find-a-memory-leak-of-a-running-process
Https://stackoverflow.com/questions/18455698/lightweight-memory-leak-debugging-on-linux
https://bugzilla.redhat.com/show_bug.cgi?id=921676
Https://stackoverflow.com/questions/2564752/examining-c-c-heap-memory-statistics-in-gdb
Http://milianw.de/blog/heaptrack-a-heap-memory-profiler-for-linux
Https://wizardforcel.gitbooks.io/100-gdb-tips/finish-and-return.html
Https://en.wikibooks.org/wiki/Linux_Applications_Debugging_Techniques/Leaks
Https://github.com/WuBingzheng/memleax
How to perform a heap profile on a running process