From: Roger Pack <rogerpack2005@...>
Date: 2009-05-09T02:04:09+09:00
Subject: Re: Ruby memory usage

>> ruby19 -e 's="."*1024;t="";loop do t << s end'
>> 
>> I.e., you can grow any String which is not frozen to arbitrary lengths.
> 
> That not really a leak, though, since t is referenced...
> 
> Not that this situation isn't a potential problem, but we should make
> sure everyone understands that the blame for it rests squarely on the
> programmer and not on ruby's GC.

In this particular case the problem definitely lies with the programmer. 
However, in some other instances ruby's GC really does stink (but 
hopefully the MBARI patches overcome its deficiencies, and also Ruby 1.9 
should have fewer problems since its threads use distinct thread memory 
spaces so can't share ghost references).
Cheers!
-=r
-- 
Posted via http://www.ruby-forum.com/.