From: matz@... (Yukihiro Matsumoto)
Date: 2002-07-13T08:08:46+09:00
Subject: Re: Wiring up the Boehm GC to the Ruby interpreter

Hi,

In message "Wiring up the Boehm GC to the Ruby interpreter"
    on 02/07/12, Matthew Bloch (by way of Matthew Bloch <mattbee@soup-kitchen.net>) <matthew@bytemark.co.uk> writes:

|Only problem was-- it leaks!  Or at least the memory use from my application
|went up and up while the standard Ruby collector kept it bounded at around
|10%.  I could tell it was doing *something* because the memory shot up much
|more quickly if I turned off collection.  Are there any 'roots' in the Ruby
|interpreter that an external GC should need to be told about?  There were no
|shared library dependencies other than the usual libc etc.  Can this *only*
|be because there's memory Boehm doesn't know about, or are there other
|pitfalls to watch out for?

gc.c allocates big chunks of memory using malloc() and chop them into
objects, so I guess you need to change rb_newobj() to use Bohem
malloc.

							matz.