[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Possible Memory Leak with stream-for-each

From: Abhijeet More
Subject: Re: Possible Memory Leak with stream-for-each
Date: Wed, 11 Aug 2010 12:57:13 -0400

On Sat, Jul 31, 2010 at 4:16 PM, Abhijeet More <address@hidden> wrote:

> Andy,
> Thanks! That's a great answer!
> I'll see what I can do with these guidelines.

Apologies - I haven't had a chance yet to look into using the libgc
library as you suggested.
Would it be possible to use valgrind massif instead of changing the
code to see what we need?

Also: I was trying to write an implementation that did not leak and
came across the following.
When I redefine "delay" and "force" as follows:
(defmacro delay (expr)
  `(make-promise (lambda() ,expr)))

(define (make-promise proc)
  (lambda() (proc)))

(define force
  (lambda (promise)

there is no memory leak. I see a leak again when I introduce
memoization into the "make-promise" implementation above.
To me it looks like that the leak that we see is caused by memoization
of the "promise" objects created by guile's default version of force
and delay. At what point does guile decide that a memoization isn't
required anymore?
At this point I don't know guile code well enough to say this for sure.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]