public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bluefoxicy at linux dot net" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/167] malloc() eats excess ram
Date: Sun, 16 May 2004 20:37:00 -0000 [thread overview]
Message-ID: <20040516203752.28384.qmail@sourceware.org> (raw)
In-Reply-To: <20040516194648.167.bluefoxicy@linux.net>
------- Additional Comments From bluefoxicy at linux dot net 2004-05-16 20:37 -------
Created an attachment (id=82)
--> (http://sources.redhat.com/bugzilla/attachment.cgi?id=82&action=view)
msztest.c -- Testcase to show how to keep the heap really huge
Should upload this too. This shows an example, albeit a controlled example, of
a program allocating a huge heap, then holding it for the sake of 100 bytes of
memory. If it were mmap() rather than current malloc(), it would free the 100M
back to the system.
Run top, then run this in a terminal next to it, and watch the state of its
memory usage at every point where it sleeps.
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=167
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2004-05-16 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-16 19:46 [Bug libc/167] New: " bluefoxicy at linux dot net
2004-05-16 19:48 ` [Bug libc/167] " bluefoxicy at linux dot net
2004-05-16 20:37 ` bluefoxicy at linux dot net [this message]
2004-05-16 20:52 ` bluefoxicy at linux dot net
2004-05-18 21:01 ` bluefoxicy at linux dot net
2004-05-27 5:09 ` bluefoxicy at linux dot net
2004-05-31 2:09 ` pinskia at gcc dot gnu dot org
2004-06-18 8:53 ` pere at hungry dot com
2004-06-20 20:17 ` bluefoxicy at linux dot net
2004-08-09 7:42 ` drepper at redhat dot com
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=20040516203752.28384.qmail@sourceware.org \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs@sources.redhat.com \
/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).