NSTimer disables dealloc in UIView

Question

@interface someview:UIView{
  NSTimer* timer;
}
@end

@implementation someview

-(void)dealloc{
  NSLog(@"dealloc someview");
  [timer invalidate];
  timer = nil;
}
-(void)runTimer{
//
}
-(void)someMethod{

  timer = [NSTimer timerWithTimeInterval:2.0f target:self selector:@selector(runTimer) userInfo:nil repeats:YES];
}

@end

Releasing someview will NOT call dealloc and the timer keeps on running.

If I comment out the "timer = [NSTimer schedule...." part, dealloc will be called. Which means all the other part of my code is working properly and the timer is the culprit. The runTimer method is empty, which means it's just the timer messing with me.

score 23 · Answer 1 · answered May 19 '11 at 18:54

I think the best solution when using an NSTimer inside of a UIView is to override the removeFromSuperview method;

- (void)removeFromSuperview
{
    [timer invalidate];
    timer = nil;

    [super removeFromSuperview];
}

The only thing to keep in mind here is that you need to ensure that timer is not a nil object because removeFromSuperview can also get automatically called from other UIView's super dealloc methods. You could wrap in a conditional to check.

removeFromSuperview will send a release message to the view. so i think we can do it in dealloc itself. — SNR, Feb 10 '12 at 06:49

score 14 · Accepted Answer · answered Apr 14 '11 at 22:30

14

NSTimer retains the target. Therefore, the timer must be invalidated before your view is dealloc'd.

answered Apr 14 '11 at 22:30

MarkPowell

16,482
7
61
77

In the superview's dealloc, i put "[someview killtimer] and [someview release], the timer got invalidated but the dealloc still doesn't get called – ssj Apr 14 '11 at 22:42
Then something else is retaining the view. – bbum Apr 14 '11 at 23:03
Don't know why the killtimer method i implemented didn't work the first time i tried it.. but it works now – ssj Apr 15 '11 at 01:10

Ash · Answer 3 · 2013-12-18T17:57:30.850

1

As mentioned above, Timers retain their targets. Until the timer is invalidated, there is a retain cycle between the timer and the view, so the view will not be deallocated.

I would invalidate the timer when it's removed from the view hierarchy by subclassing didMoveToSuperview, this gets called by the system when there is a View-Related Change (e.g superview changes). The 'removeFromSuperview' is only called when removeFromSuperview is called on UIView

- (void)didMoveToSuperview
{
    [super didMoveToSuperview];

    if (!self.superview)
    {
        [timer invalidate];
        timer = nil;
    }
}

edited Dec 18 '13 at 17:57

answered Dec 18 '13 at 15:28

Ash

411
6
13

The problem is not necessarily caused by a retain cycle. Even if you have a weak (or no) reference to the timer, the timer will be retained by the run loop it's scheduled in. – Anthony Mattox Feb 12 '15 at 20:19

NSTimer disables dealloc in UIView

3 Answers3

Linked