From: Marius Nita <marius@cs.pdx.edu>
To: linux-c-programming@vger.kernel.org
Subject: gc
Date: Fri, 22 Nov 2002 13:54:32 -0800 [thread overview]
Message-ID: <20021122215432.GA13869@cs.pdx.edu> (raw)
hi,
i was wondering if anyone here has had any experience with the Boehm garbage
collector (libgc).
i noticed that while it does seem to collect memory correctly, the
reclaimed space is not shown by tools like ps and top. in a program, when you
call free(), system memory is automatically adjusted. (as shown by these
tools.) but when using the gc, say you allocate 10 megs, invalidate the
pointer to this memory and invoke the collector explicitly, these 10 megs are
reclaimed, but your process still shows up as using 10 megs... i don't know
how ps and top work, but if they rely on calls to free() to shrink usage
accordingly, that might explain it; since libgc implements its own allocators
on top of sbrk.
i don't think this is a huge issue, just wondering if anyone knows of a way
around it.
thanks
marius
next reply other threads:[~2002-11-22 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 21:54 Marius Nita [this message]
2002-11-23 5:32 ` gc Glynn Clements
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=20021122215432.GA13869@cs.pdx.edu \
--to=marius@cs.pdx.edu \
--cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).