Re: PropertyLocks?: strange exc_bad_access crash
Re: PropertyLocks?: strange exc_bad_access crash
- Subject: Re: PropertyLocks?: strange exc_bad_access crash
- From: Graham Cox <email@hidden>
- Date: Tue, 10 Aug 2010 03:20:06 +1000
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
_______________________________________________
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