public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nicolas at freedelity dot be" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug malloc/30579] trim_threshold in realloc lead to high memory usage Date: Thu, 06 Jul 2023 16:09:17 +0000 [thread overview] Message-ID: <bug-30579-131-xhzyfAB4PD@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30579-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30579 --- Comment #8 from Nicolas Dusart <nicolas at freedelity dot be> --- Thanks a lot for the fix in 2.37 branch ! -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2023-07-06 16:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-22 13:54 [Bug malloc/30579] New: " nicolas at freedelity dot be 2023-06-22 14:20 ` [Bug malloc/30579] " siddhesh at sourceware dot org 2023-06-22 15:10 ` nicolas at freedelity dot be 2023-06-28 7:56 ` nicolas at freedelity dot be 2023-06-28 16:31 ` siddhesh at sourceware dot org 2023-07-06 15:38 ` cvs-commit at gcc dot gnu.org 2023-07-06 15:40 ` cvs-commit at gcc dot gnu.org 2023-07-06 15:42 ` siddhesh at sourceware dot org 2023-07-06 16:09 ` nicolas at freedelity dot be [this message]
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-30579-131-xhzyfAB4PD@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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).