Re: [Rubycocoa-talk] Is there any benefit of explicitly calling release?

[Jonathan d. S. <mai...@st...>]

A while back, rmagick had 'leaks' where, if I remember correctly, it
would allocate a huge chunk of memory on the C side of things for
loading the image.  The ruby code would finish with its handle to the
image, and the handle would end up in the garbage collection bin.
Once the handle was disposed, the image buffer memory would be
correctly deallocated.  So, not a leak as such, but the problem
appeared because ruby doesn't bother GCing until it reaches 8MB of
uncollected stuff, IIRC.  Ruby's collector only knew about the size of
the handle (ie a 4 byte pointer), and knew nothing about the huge
buffer connected to it on the C side of the bridge, so garbage
collection was never triggered.

Now... I have no idea if that applies at all to rubycocoa, but is it
possible that's along the lines of what you're seeing?


On Tue, Jul 29, 2008 at 10:10 AM, Tim Perrett <he...@ti...> wrote:
> Sorry for the late reply - I've just got around to doing this. It
> appears that over time, all the objects are increasing there memory
> footprint?
>
> It almost looks like RC is not releasing them at all?
>
> Cheers
>
> Tim
>
>
> On 25 Jul 2008, at 18:18, Chris McGrath wrote:
>
>> Tried running it under instruments to see what's increasing?
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
>