From: Michael Neumann <mneumann@...>
Date: 2005-01-20T04:36:59+09:00
Subject: Re: 1.8.2 - conituations memory leak fixed?

Am Mittwoch 19 Januar 2005 19:35 schrieb Eric Hodel:
> On 19 Jan 2005, at 08:15, Michael Neumann wrote:
> > Am Mittwoch 19 Januar 2005 16:53 schrieb ts:
> >>>>>>> "j" == jc  <james.cromwell@gmail.com> writes:
> >>
> >> j> This was posted recently:
> >> j> http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/124213
> >>
> >>  This is the proof that the GC is conservative, this does not mean
> >> that it
> >>  exist a memory leak.
> >
> > Sure, but the results might be the same ;-)
>
> I don't see a callcc in there anywhere, so
> callback_stream.with_callbacks_for could be doing other naughty things.

Right. But it's the place where the callbacks are invoked. And the callback 
that gets invoked actually uses callcc. It was very strange that, when I 
change that line in some manner (introduce an assignment), the memory 
consumption changes drastically.

>   From personal experience with callcc, I would bet on something
> referencing live objects over any memory leaks.

I think the problem is due to the conservative GC. But of course, there might 
also be some bugs in it (but then, memory consumption should be unbounded as 
well, if I remove continuations, which I've done).

Regards,

  Michael