From: Abhijeet More <abhijeet.more@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Possible Memory Leak with stream-for-each
Date: Sat, 24 Jul 2010 12:32:59 -0400 [thread overview]
Message-ID: <AANLkTikLS1yn04_hDW=dMeRxBB4enZPbeLFwK2_S5snJ@mail.gmail.com> (raw)
In-Reply-To: <87iq44yi1q.fsf@gnu.org>
On Sat, Jul 24, 2010 at 12:13 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hi!
>
> The leak you describe seems to be that depicted under “Why the space
> leak occurs” at <http://srfi.schemers.org/srfi-45/srfi-45.html>.
>
> Am I right?
I don't think so. The leak described in SRFI-45 is due to a naive
implementation of stream-filter on SICP-like streams (odd or even).
SRFI-45 describes a way to implement streams so that the leak does not
occur with the naive implementation of stream-filter.
The leak I'm referring to happens with *stream-for-each*.
*stream-filter* is not involved in any way.
I doubt if that is the problem I'm describing - especially since the
same code doesn't cause a leak in PLT Scheme/Racket.
Thanks
Abhijeet
next prev parent reply other threads:[~2010-07-24 16:32 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 [this message]
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
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='AANLkTikLS1yn04_hDW=dMeRxBB4enZPbeLFwK2_S5snJ@mail.gmail.com' \
--to=abhijeet.more@gmail.com \
--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).