public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
* How to track size of malloc internal caches?
@ 2020-07-27 12:31 Anton Zyablitskiy
  0 siblings, 0 replies; only message in thread
From: Anton Zyablitskiy @ 2020-07-27 12:31 UTC (permalink / raw)
  To: libc-help

Hi Glibc team,

I have a slow memory depletion (100-300 kb per hour) on my long running
highly multithreaded app and suspect allocator internal caches or
fragmentation. By internal caches I understand those memory which was freed
by application but kept by malloc for later use. I need a way to prove or
disprove this.
I collected malloc_info output over certain time intervals but it is hard
to understand.
Could you please point me to numbers I should look at? Maybe there are some
aggregate numbers like 'total allocated from os' or 'total in use by
application'?
If it possible it is preferred to use something other than malloc_info
because it crashes my app with "*Bug 22408* - malloc_info access heaps
without arena lock, ignores heaps"
I use glibc 2.23 on a 64-bit linux system.

Thank you!
-AntonZ

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-07-27 12:32 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-27 12:31 How to track size of malloc internal caches? Anton Zyablitskiy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).