From: Abhijeet More <abhijeet.more@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-user@gnu.org
Subject: Re: Possible Memory Leak with stream-for-each
Date: Thu, 29 Jul 2010 20:38:30 -0400 [thread overview]
Message-ID: <AANLkTik0SSM12==nfyEHcUudO5esB+5aPxoZ19B4gN0-@mail.gmail.com> (raw)
In-Reply-To: <m3r5iqinz3.fsf@unquote.localdomain>
On Mon, Jul 26, 2010 at 5:36 AM, Andy Wingo <wingo@pobox.com> wrote:
>
> I think it's probably our bug, but I haven't had time to examine it
> thoroughly.
FWIW - I tried using the SRFI-45 reference implementation for delay
and force (as-is from the SRFI reference implementation) and got the
same behavior.
To debug this further are there any useful places in the
stream-for-each implementation that I could do a gc-stats from? Or
would we need to look at the C implementation?
Can anyone suggest good starting points for this?
Thanks
Abhijeet
next prev parent reply other threads:[~2010-07-30 0:38 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 [this message]
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
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='AANLkTik0SSM12==nfyEHcUudO5esB+5aPxoZ19B4gN0-@mail.gmail.com' \
--to=abhijeet.more@gmail.com \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.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).