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 18:27:42 +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 #4 from Yichao Yu <yyc1992 at gmail dot com> ---
> And this does not seem to be a GLIBC issue based on the example provided
It is, since the memory consumption (measured by overall system memory usage
and also the maxrss of the process) grows much faster than what the actual
accumulated memory does (by more than 100x).
> Also, if you ran the example on valgrind you see it does have a lot of actual memory leaks (which I am not sure if they are intentional or not for the example itself).
Yes it will obviously detect leaks since the program does not free all the
memory it allocates. As mentioned in the original report and above though, that
small amount of accumulated allocation is causing a much higher memory
consumption increase (measured by overall system memory usage and also the
maxrss of the process).
--
You are receiving this mail because:
You are on the CC list for the bug.