From: matz@... (Yukihiro Matsumoto)
Date: 2004-05-19T08:10:14+09:00
Subject: Re: (fwd) [Borges-users] memory strikes back!

Hi,

In message "(fwd) [Borges-users] memory strikes back!"
    on 04/05/11, Michael Neumann <mneumann@ntecs.de> writes:

|Can anyone of the Ruby experts tell us where the memory leak might be?

Ruby uses conservative garbage collection, which scans C stack and
considers the value suspicious to be a pointer as a pointer.  In this
case, perhaps, some unused junk saved in the stack copy in the
continuation object refers to the object, which is a target of a
weakref.  I will try something, but it's hard to promise to fix.

							matz.