From: Roger Pack <rogerpack2005@...>
Date: 2009-07-23T22:49:20+09:00
Subject: Re: Garbage collection oddities

> That is, on 1.9.1, the object is never collected.

The kicker here is it may not be a bug--it may be that there is a "ghost 
reference" to the object still kicking around somewhere [on the stack or 
what not].
Because the C calls internally sometimes have extra references that 
aren't used, they don't clean the whole stack just by using it, so 
sometimes references are left there.

You could try going down deep in the stack then creating your objects
def go(n)
 if n==100
   # do something
 else
   go(n+1)
 end
end

go(0)
GC.start

and see if that helps.

In general, however, you're not guaranteed that finalizers will be 
called at any point--only guaranteed that they'll be called before the 
program exits (I think that's what happens anyway).
GL!
=r
-- 
Posted via http://www.ruby-forum.com/.