From: matz@... (Yukihiro Matsumoto)
Date: 2001-08-12T23:48:52+09:00
Subject: [ruby-talk:19605] Re: Forced garbage collection

Hi,

In message "[ruby-talk:19550] Forced garbage collection"
    on 01/08/12, Lars Christensen <larsch@cs.auc.dk> writes:

|This code tell me that Foo 1 is still there after the garbage collection
|has been invoked. If i change the order of the Foo.new calls to:
|
|f = Foo.new(2); f = nil
|Foo.new(1)
|
|Then, both Foo 1 and Foo 2 are in memory after garbage collection.
|
|I cannot reproduce on Solaris (both intel and sparc). Here, all the object
|gets deleted.
|
|Why this behaviour? A bug?

Ruby uses conservative GC, which leaves garbages unreclaimed if in
doubt.

							matz.