From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Possible Memory Leak with stream-for-each
Date: Thu, 02 Sep 2010 11:46:47 -0700 [thread overview]
Message-ID: <m3y6bkt23s.fsf@unquote.localdomain> (raw)
In-Reply-To: <8762yoe2eo.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 02 Sep 2010 14:49:19 +0200")
On Thu 02 Sep 2010 05:49, ludo@gnu.org (Ludovic Courtès) writes:
> Basically ‘force’ was leaking memory because it uses ‘lock-mutex’, which
> was the culprit (!).
You are a superhero, Dr. Courtès!!
A
--
http://wingolog.org/
prev parent reply other threads:[~2010-09-02 18:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 18:08 Possible Memory Leak with stream-for-each Abhijeet More
2010-07-20 20:36 ` Andy Wingo
2010-07-21 7:00 ` Tristan Colgate
2010-07-24 16:13 ` Ludovic Courtès
2010-07-24 16:32 ` Abhijeet More
2010-07-24 16:46 ` Abhijeet More
2010-07-26 9:36 ` Andy Wingo
2010-07-30 0:38 ` Abhijeet More
2010-07-31 11:48 ` Andy Wingo
2010-07-31 20:16 ` Abhijeet More
2010-08-11 16:57 ` Abhijeet More
2010-08-02 3:29 ` Tibi Turbureanu
2010-08-15 15:12 ` Heap profiler Ludovic Courtès
2010-09-02 12:49 ` Possible Memory Leak with stream-for-each Ludovic Courtès
2010-09-02 16:20 ` Julian Graham
2010-09-02 18:46 ` Andy Wingo [this message]
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=m3y6bkt23s.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=ludo@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).