I haven't followed this whole thread, but my experience is that an NSTimer (especially a repetitive one) is an easy thing to leak, even in a GC environment (which I use). To prevent it, you have to make sure you keep a reference to the timer so that you can actually invalidate it, taking it out of the run loop. Otherwise, it stays there forever.
On 3/13/10 2:02 PM, "cocoa-dev-requ...@lists.apple.com" <cocoa-dev-requ...@lists.apple.com> wrote: > For the benefit of the OP, according to the docs (and this fits in with my own > experience), calling [NSTimer invalidate] will release the timer at some > future point in the run loop and is in fact the only way to get rid of it. So > there is really nothing to worrry about. Trust in Papa Cocoa, all will be > well. _______________________________________________ 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
