public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jtaylor.debian at googlemail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/17195] excessive heap trimming in threaded programs even when disabled with mallopt
Date: Sat, 30 Aug 2014 12:40:00 -0000	[thread overview]
Message-ID: <bug-17195-131-oNXVQ6qUWt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17195-131@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Julian Taylor <jtaylor.debian at googlemail dot com> ---
my issue is not with sbrk but with madvise in threaded applications which
cannot be worked around by using mallopt like in the other bug.
the trimming can be disabled in single threaded applications but not
multithreaded ones.

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


  parent reply	other threads:[~2014-08-30 12:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 11:04 [Bug malloc/17195] New: excessive heap trimming in threaded programs jtaylor.debian at googlemail dot com
2014-07-24 11:07 ` [Bug malloc/17195] excessive heap trimming in threaded programs even when disabled with mallopt jtaylor.debian at googlemail dot com
2014-08-30 12:34 ` neleai at seznam dot cz
2014-08-30 12:40 ` jtaylor.debian at googlemail dot com [this message]
2015-02-12 17:46 ` jtaylor.debian at googlemail dot com
2015-02-18  5:48 ` siddhesh at redhat dot com
2015-04-02  6:46 ` cvs-commit at gcc dot gnu.org
2015-04-02  6:48 ` siddhesh at redhat dot com
2015-10-08  2:23 ` cvs-commit 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-17195-131-oNXVQ6qUWt@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: link
Be 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).