> Take a look at the stack trace again. It's happening within the call > to +[NSTimer scheduledTimerWithInterval:target:selector:userInfo:repeats:]. > The problem can't be that he hasn't retained a timer he hasn't > created yet.
The problem is that he's corrupted the heap, which could have happened by using the prior timer after it had been dealloc'd. Or any other memory error, possibly not related at all to NSTimer. -- Scott Ribe scott_r...@killerbytes.com http://www.killerbytes.com/ (303) 722-0567 voice _______________________________________________ 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
