Doug Alcorn wrote:
> Igal Koshevoy wrote:
> 
>> Can you or one of your engineers try to figure out how to trigger this
>> memory ballooning problem? That'd be really valuable to the Ruby 
>> community.
>>
> 
> Not only to the community, but also my client.  I've been working on it 
> on and off for several weeks.  I'm not sure I have the right skills atm 
> to do memory profiling.  I'd be interested in some good pointers on how 
> to memory profile ruby/rails apps

I've never used it, but I believe "valgrind" is the tool one uses to 
check for memory leaks in C code -- like MRI, for example. :)