From: Na Na <lists@...>
Date: 2013-01-14T09:43:20+09:00
Subject: Re: Garbage Collection and Fibers

Aha.  I realised that running it in a separate thread or fiber would
mean it would miss some objects, but I was thinking that would mean it
may not deallocate them when it should, which I didn't care so much
about.  I didn't think that it might cause some to be deallocated when
they shouldn't!

So I suppose my options are:
* Call GC only when suits me, and put up with the slowness as a part of
life
* Reduce the number of objects I use
* Tweak the GC settings so that it's needed to be called less frequently
(but I suspect this will just postpone my issues)
* Try ruby 2.0's GC
* Use something other than ruby for my app (nowhere near an ideal
option!)

-- 
Posted via http://www.ruby-forum.com/.