From: Tom Moulton <lists@...>
Date: 2012-04-05T20:06:09+09:00
Subject: Not a Memory Leak but Stale Objects - clears with GC.start

I have a long running process.

When it gets busy the memory the task uses grows from
300-400MB to  1.2-1.8GB

So I thought I had a leak... but when I do a GC.start
(Garbage Collection start)
the memory usage (shown by 'top') drops back to normal.

As a temporary solution I have the GC.start run once a minute and then
I started thinking...

I see a lot of threads pointing out problems with Ruby memory management
and garbage collection, so might this solution be ok to continue to use?

There is only one main loop, the rest are periodic calls
to Proc objects.

I thought when a function returns any stale objects could be released.
(And in fact they are when I call GC.start, so something else is
causing GC not to start on it's own)

I am running Debian linux and have

ruby 1.8.7 (2010-08-16 patchlevel 302) [i486-linux]

I know there are newer versions of ruby,
but don't want to upgrade just yet...

just lazy I guess :)

tom

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