[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] chicken-fuse

From: Thomas Chust
Subject: Re: [Chicken-hackers] chicken-fuse
Date: Tue, 18 Mar 2014 11:33:49 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0

On 2014-03-18 08:56, Evan Hanson wrote:
> [...]
> My thinking was that, because the release
> callback is used to clean up resources, one would want it to receive the
> handle value in a form that's already as cleaned up as possible from
> fuse's point of view (i.e. unevicted).
> [...]


as far as I can tell and if I understand the CHICKEN manual correctly,
object-unevict copies an object into garbage collected memory but does
*not* destroy the original evicted copy.

So, unless this release callback of yours also frees the evicted copy
using the deallocator function matching the allocator function that was
passed to the original call to object-evict, this will very likely leak
resources *and* perform unnecessary managed allocation operations during


When C++ is your hammer, every problem looks like your thumb.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]