This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug malloc/21731] Bad malloc heuristic result in 30-40x memory consumption
- From: "yyc1992 at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 11 Jul 2017 19:49:45 +0000
- Subject: [Bug malloc/21731] Bad malloc heuristic result in 30-40x memory consumption
- Auto-submitted: auto-generated
- References: <bug-21731-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21731
--- Comment #10 from Yichao Yu <yyc1992 at gmail dot com> ---
As I said in the very first post, the program does have a small "leak".
However, I think it is reasonable to expect that if the program allocate <100kB
per loop, the peak memory consumption (measured by overall system memory usage
and also the maxrss of the process) should not grow 10x or 100x faster than
this "leak". It is perfectly valid in a program to accumulate small allocations
overtime until they are free'd later. Being able to return to the same memory
consumption (measured in whatever way) is not the only measure of a bug-free
memory manager, the ratio between the peak memory usage and the memory actually
needed is too.
--
You are receiving this mail because:
You are on the CC list for the bug.