On May 1, 2010, at 20:42, James Maxwell wrote: > So, looking more closely at the NSArray itself in the debugger, the items in > the array come up as > > 0 NSCFNumber* > 1 NSCFNumber* > 2 NSObject* > 3 _NSZombie_CFNumber* > 4 NSObject*
This strongly suggests a memory management problem -- something is over-releasing the items in the array. On May 1, 2010, at 21:22, James Maxwell wrote: > If I drop into the debugger arbitrarily, before the crash, and check this > same array, I noticed that it is nicely filled with NSCFNumbers. But, > strangely, there are too many. My guess is that you've still got multiple threads accessing the mutable array simultaneously, and that's not thread-safe if one of the accesses is changing the array. You're fighting this battle on too many fronts. You've got a "sketchy" grasp of GCD, you're uncertain whether you're actually multithreading or not, and this sort of let-everything-poke-every-object-from-every-direction application design really makes it to determine correctness. Probably you should pick one thing, and comment everything else out, until you're sure that small part is working. Then add the complexity back in slowly, checking correctness at each step. FWIW. _______________________________________________ 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
