Re: NSTimer never being deallocated
Re: NSTimer never being deallocated
- Subject: Re: NSTimer never being deallocated
- From: Dave Keck <email@hidden>
- Date: Sat, 13 Mar 2010 08:21:08 -1000
>> Recycled objects can appear as leaks, making it hard to distinguish
>> between a bug and normal behavior.
>
> I don't think that's true (it doesn't fit with the algorithm used for identifying leaks), but if it is, please file a bug report:
I didn't mean to imply the Leaks instrument. Using the ObjectAlloc
instrument to find rooted leaks, for example, and seeing a steady
increase of NSNumber and NSString objects leads one to believe there's
a leak, when in fact the objects are just being cached. Of course I
don't think anyone would consider this a bug - just something that
needs to be kept in mind.
_______________________________________________
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