From: Jason Roelofs <jameskilton@...>
Date: 2007-06-14T03:15:25+09:00
Subject: Re: Manual Garbage Collection

------=_Part_28882_12929892.1181758526779
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

You can GC.start to run it manually. If you can I'd recommend trying to
figure out what object is getting improperly GC'd and let the Ruby-Gnome2
team know about this. I've seen this kind of thing happen when Ruby tries to
send it's own objects back into the underlying library. For me it was Ruby
subclasses of C++ classes and dealing with setting listener objects.

Jason

On 6/13/07, Conan <spam@woodsc.ca> wrote:
>
> Hi.  I'm having a problem with a Ruby-Gnome2 application I've been
> building.  For some reason(which I haven't identified but I suspect is
> ruby-gnome problem) my program randomly segfaults.  I fixed this by
> disabling garbage collection(Maybe GC was cleaning up objects that were
> still in use?) but of course now my application runs out of memory
> relatively quickly.  I know which parts of my non-gnome related code are
> memory hogs, and I was wondering if there is a way to manually garbage
> collect specific objects(and their dependencies hopefully)?  Or,
> alternatively, is their a way to only run garbage collection within a
> certain scope?
>
> I'd love a solution to this, as my current alternatives are either
> running out of memory or random segfaults.
>
> --
> Posted via http://www.ruby-forum.com/.
>
>

------=_Part_28882_12929892.1181758526779--