On Aug 9, 2010, at 11:48, James Maxwell wrote: > Sorry, no, the initWithCoder happens at program launch, in the main thread - > nothing fancy there.
You said "It only happens when running a particular function from its saved state (i.e., from initWithCoder)". That "when" and "from" made it sound very much as if you were creating the background thread in initWithCoder. But never mind, that's apparently not what you meant. The backtrace suggests that either: a. It's trying to acquire a lock on the 'inputMemory' property of the HSMM_Sequencer object. b. It's trying to acquire a lock on a property of an object that's in the 'inputMemory' array. Either way, you likely have one of these problems: 1. Your archive was decoded correctly, but the encode was incorrect. 2. Your archive was decoded incorrectly (or incompletely). 3. You inadvertently have a threading error that destroys an object's internal state, which could relate to any object in the archive. 4. You inadvertently over-released something and therefore have a pure memory management error, which could relate to any object in the archive. So you have a bit of work to do to pin it down, perhaps by validating your archive more thoroughly somewhere. Nothing but debugging will get you any further with this, I think. _______________________________________________ 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 arch...@mail-archive.com
