public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/53169] Memory leak in std::vector<std::vector*> Date: Mon, 30 Apr 2012 14:59:00 -0000 [thread overview] Message-ID: <bug-53169-4-B1MksOt9D1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53169-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53169 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-04-30 14:59:05 UTC --- By changing your main to: int main() { test(); sleep(10); char* p = (char*)malloc(1024 * 127); for (int i=0; i < 100; ++i) p[1024 * i] = 'a' + (i%26); sleep(10); free(p); sleep(10); return 0; } I see that freeing the small malloc'd memory region (which is below glibc's MMAP_THRESHOLD value) does actually trigger the earlier new'd memory to be returned to the system too. So it's possible to get the memory libstdc+ allocates to be returned to the system, but it's under the control of glibc, nothing to do with std::vector or libstdc++ If your memory usage patterns don't result in memory being returned then there are several posibilities, including not freeing memory when you think you are, or fragmenting the heap so that later allocations cannot re-use memory returned to freelists and must allocate new memory using mmap. Not a GCC bug though.
next prev parent reply other threads:[~2012-04-30 14:59 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-30 14:06 [Bug libstdc++/53169] New: " antoinep92 at gmail dot com 2012-04-30 14:28 ` [Bug libstdc++/53169] " redi at gcc dot gnu.org 2012-04-30 14:59 ` redi at gcc dot gnu.org [this message] 2012-04-30 15:13 ` redi at gcc dot gnu.org 2012-04-30 15:16 ` redi at gcc dot gnu.org 2012-04-30 15:27 ` antoinep92 at gmail dot com 2012-04-30 15:31 ` antoinep92 at gmail dot com 2012-04-30 15:52 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-53169-4-B1MksOt9D1@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).