unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: mark@markwitmer.com
To: guile-user@gnu.org
Subject: Memory use analysis
Date: Tue, 13 Aug 2013 14:23:08 -0400	[thread overview]
Message-ID: <877gfpxxf7.fsf@markwitmer.com> (raw)


I'm facing an issue with ballooning memory usage in a progam I'm writing
and having a difficult time tracking down the root cause. The stack
stays small but it uses more and more heap space until the system runs
out of memory.

Is there some kind of tool or method for getting Guile to enumerate what
objects in the heap are considered "live" by the GC? I guess the
conservative GC Guile uses doesn't explicitly keep track of every
object, but I wouldn't mind just being able to see what stuff in the
heap it *thinks* it needs to keep, and then query what kind of SCM
objects they represent.

Thanks

-- 
Mark Witmer



             reply	other threads:[~2013-08-13 18:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 18:23 mark [this message]
2013-08-19 14:09 ` Memory use analysis Ludovic Courtès
2013-09-07  9:46 ` Andy Wingo

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877gfpxxf7.fsf@markwitmer.com \
    --to=mark@markwitmer.com \
    --cc=guile-user@gnu.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).