I have added a call to CFMakeCollectable each time after I create a CF
object like this
CFSomeTypeRef a = CFCreateSomeType();
if (a != nil)
{
CFMakeCollectable(a);
}
But I keep getting this runtime message in the console:
malloc: reference count underflow for 0x10773c0, break on
auto_refcount_underflow_error to debug.
All CF objects I create are local vars in scope of one single
function, no instance or global vars. I create several CF objects,
some of them are used as arguments for other functions. The error is
issued only for one of the CF objects I create, the other work fine.
What can be the problem?
On Mon, Aug 11, 2008 at 3:25 PM, Antonio Nunes <[EMAIL PROTECTED]> wrote:
> On 11 Aug 2008, at 13:14, Antonio Nunes wrote:
>
>>> Will it cause a memory leak if I treat the Quartz object in the same
>>> way as I do to all my NSObject descendants, i.e. no retains and rely
>>> only on garbage collection?
>>
>> You either take care of the object's life time manually as you would in a
>> non-garbage collected environment, or you explicitly move it into the realm
>> of the garbage collector. Lookup "CFMakeCollectable" and "NSMakeCollectable"
>> in the docs.
>
> I should add: read the "Memory Management Semantics" in "Using Core
> Foundation with Garbage Collection" in the "Garbage Collection Programming
> Guide", which has a thorough explanation of how to handle CF objects under
> GC.
>
> António
>
> ----------------------------------------------------
> It isn't so important to do great things,
> as to do what you do with great love.
> ----------------------------------------------------
>
>
>
>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
