heh... yeah, that's true. But the thing is I haven't done anything different with this particular float* array. It's the same type of archiving I've used at many points in the app. But I hadn't thought to look for weak references.... could this be as simple as making sure to type cast objects when adding them to mutable arrays?
J. On 2010-08-01, at 1:19 PM, Quincey Morris wrote: > On Aug 1, 2010, at 12:30, James Maxwell wrote: > >> What I don't understand is how the Hierarchy can be fine at the end of the >> Network's initWithCoder method, but then get banjaxed somehow after that. > > Sure you do. Things disappear suddenly when not retained or strongly > referenced. You're describing one of the classic manifestations of a memory > management error. > > > _______________________________________________ > > Cocoa-dev mailing list ([email protected]) > > 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/jbmaxwell%40rubato-music.com > > This email sent to [email protected] James B Maxwell Composer/Doctoral Student School for the Contemporary Arts (SCA) School for Interactive Arts + Technology (SIAT) Simon Fraser University [email protected] [email protected] _______________________________________________ Cocoa-dev mailing list ([email protected]) 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]
