From: Joel VanderWerf <vjoel@...>
Date: 2009-05-09T01:24:01+09:00
Subject: Re: Ruby memory usage

Robert Klemme wrote:
> Btw, you can easily construct a memory leak, which cannot necessarily
> be detected by counting objects:
> 
> 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.

-- 
       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407