[Bug malloc/21731] Bad malloc heuristic result in 30-40x memory consumption

["adhemerval.zanella at linaro dot org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=21731

--- Comment #13 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Carlos O'Donell from comment #11)
> (In reply to Adhemerval Zanella from comment #8)
> > The main problem is the example you provided is *leaking* memory and using
> > this an a driver to state that glibc is resulting in increase memory
> > consumption does not make sense. Either you need to provide an example that
> > does not leak memory and thus shows that this is indeed an internal glibc
> > issue or fix it in your program.
> 
> You can have an application that allocates a cache and does not free the
> cache. So from the glibc allocator perspective it is not leaking memory,
> it's just not being returned because it could be in use. So asking for a
> perfect program that doesn't leak just results in a slightly altered test
> case that has roughly the same semantics anyway.

And that was not clear neither from the initial bug report nor on subsequent
comments. Neither in original project bug report I could get some insight from
these initial '~1.6kb' leaks came from of for what the memory is used. So I
assumed that this indeed a faulty memory leak.

> 
> The question that remains is:
> 
> Where is the memory going?
> 
> * external/internal malloc fragmentation?
> * program requirements growing with time?
> * an application leak?
> 
> You have to answer one of these three questions.

Thanks for the summary Carlos, I think this is pretty much the information lack
we need to move forward.

-- 
You are receiving this mail because:
You are on the CC list for the bug.