public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sakovacs at freemail dot hu" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/2531] missing call or documentation for malloc_trim() ...
Date: Wed, 26 Apr 2006 11:35:00 -0000	[thread overview]
Message-ID: <20060426113521.7658.qmail@sourceware.org> (raw)
In-Reply-To: <20060409085351.2531.sakovacs@freemail.hu>


------- Additional Comments From sakovacs at freemail dot hu  2006-04-26 11:35 -------
  
> a) libc returns all memory if malloc_trim is used  
  
I agree. That's what I said too:  
>... if you call malloc_trim(0) right before the usleep() the RSS goes back to   
> less than 1M (this is a simple case, no fregmentation, all memory could be   
> returned to the OS).  
  
b) the kernel frees all memory.  
  
I agree with this as well.  
  
> So, what's the problem?  
  
All I was saying is that either put malloc_trim() should be referenced in the  
malloc/free man page or free() should call it from time to time -- I since  
read that this should be the case. So a simple "see also" entry would help a 
lot for many guys having similar issues.  
  
Cheers,  
Sandor  
  
  

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2531

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-04-26 11:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-09  8:53 [Bug libc/2531] New: " sakovacs at freemail dot hu
2006-04-09  8:55 ` [Bug libc/2531] " sakovacs at freemail dot hu
2006-04-26  2:15 ` drepper at redhat dot com
2006-04-26 11:35 ` sakovacs at freemail dot hu [this message]
2006-05-01 18:41 ` 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=20060426113521.7658.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --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).