From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: plugged a memleak
Date: Wed, 21 Mar 2012 22:02:55 +0100 [thread overview]
Message-ID: <87iphx8y68.fsf@gnu.org> (raw)
In-Reply-To: 87haxllkzr.fsf@pobox.com
Hi!
Andy Wingo <wingo@pobox.com> skribis:
> I just fixed a long-standing memory leak in Guile 2.0. (I say that like
> I'm proud or something, but of course I was the one the introduced it in
> the first place!)
Excellent!
> See c05805a4ea764dec5a0559edefcdfb9761191d07 in stable-2.0 for the
> gnarly details. The summary is that applicable smobs were being leaked,
> because they were referenced in the values of weak-key tables.
I was wondering whether removing ‘smob-call’ would break binary
compatibility, but presumably that instruction could not possibly end up
in user bytecode on disk, right?
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-03-21 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 20:20 plugged a memleak Andy Wingo
2012-03-21 21:02 ` Ludovic Courtès [this message]
2012-03-21 22:03 ` Andy Wingo
2012-03-23 18:03 ` Ludovic Courtès
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=87iphx8y68.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).