You do know about autorelease pools, right? See whether the object survives the next event cycle. I'm betting it doesn't.
Retain counts are none of your business, as is repeated almost daily on this list. Don't peek at them, infer nothing from them. Follow the ownership rules, and you'll be fine. You can perform clean-up when the object is deallocated (NOT released, that's absolutely not the same thing - performing clean-up at release time is a sure route to disaster) by overriding -dealloc. --Graham On 19/07/2011, at 12:17 AM, Ryan Joseph wrote: > I wonder why Cocoa has retained it 4 times and what it plans to do with it > since I don't see thing that will cause the memory to be released. _______________________________________________ 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
