Re: PropertyLocks?: strange exc_bad_access crash
Re: PropertyLocks?: strange exc_bad_access crash
- Subject: Re: PropertyLocks?: strange exc_bad_access crash
- From: James Maxwell <email@hidden>
- Date: Mon, 9 Aug 2010 10:42:42 -0700
Yes, so I always use accessors in my initWithCoder routines. Is that a bad idea?
My assumption was that the accessor would take care of the retain (most of these are synthesized, retaining accessors, though some are hand-written accessors -- but they should all be retaining).
I'll double-check everything again, but I'm pretty sure all the initWithCoders should be retaining.
J.
On 2010-08-09, at 10:20 AM, Graham Cox wrote:
>
> On 10/08/2010, at 3:07 AM, James Maxwell wrote:
>
>> What's strange, to me, is that if this is a threading problem, why does it only happen from a decoded state, not from a clean inited state?
>
>
> More likely to be a memory management problem. You're aware that objects returned by -decodeObjectForKey: are autoreleased?
>
> Set a breakpoint at the start of -inputMemory and step until it crashes. Then you know the errant line. Perhaps the property you're setting from the result of the decode is incorrectly specified. Dunno - show your code.
>
> --Graham
>
>
James B Maxwell
Composer/Doctoral Student
School for the Contemporary Arts (SCA)
School for Interactive Arts + Technology (SIAT)
Simon Fraser University
email@hidden
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden