NSTimer crash with EXC_BAD_ACCESS on Iphone when invalidate

Question

I have setup two timers in my application which both repeats every a few seconds. Everything works fine except when is time to invalidate the timers. When the phone is locked, I want to invalidate those timers and then recreate them when the phone is unlocked.

Im using the notifications to realize when to invalidate/create the timers.

    [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(notify_didBecomeActive:) name:UIApplicationDidBecomeActiveNotification object:nil];
    [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(notify_willResigneActive:) name:UIApplicationWillResignActiveNotification object:nil];

This is what the notify_didBecomeActive method contains:

clockTicker = [[NSTimer scheduledTimerWithTimeInterval: 1  
                                            target: self  
                                          selector: @selector(showActivity)  
                                          userInfo: nil  
                                           repeats: YES] retain];

alarmTicker = [[NSTimer scheduledTimerWithTimeInterval: CONST_ALARMTIMER  
                                               target: self  
                                             selector: @selector(checkAndLaunchAlarm)  
                                             userInfo: nil  
                                              repeats: YES] retain];

This the notify_willResigneActive method contains:

if (alarmTicker) {
    [alarmTicker invalidate];
    [alarmTicker release];
    alarmTicker = NULL;
}

if (clockTicker) {
    [clockTicker invalidate];
    [clockTicker release];
    clockTicker = NULL;
}

The problem is that when I debug this on the second timer invalidate I get the error. The weird thing is that if I switch the orders of the timers (like first invalidate the clockTicker).. I still got the error on the second timer.

What could I be doing wrong?

Thanks, Leonardo

Daniel · Accepted Answer · 2009-09-18T18:44:34.183

5

invalidate releases the timer, no need to release after invalidating, thats why its crashing. But i just noticed that you are retaining the timer...im not sure that this is necessary either.

edited Sep 18 '09 at 18:44

answered Sep 18 '09 at 18:38

Daniel

22,363
9
64
71

Maybe.. but either way it does not work. Is the second timer that crashes, not the release line. I can't get much information.. will try to enable the zombies to see if there is something I'm missing. – Homer1980ar Sep 22 '09 at 17:29

score 0 · Answer 2 · answered Aug 03 '12 at 18:52

0

You just need to set alarmTicker and clockTicker to nil inside the methods that those timers fire and that way when you do your check if (alarmTicker) or if (clockTicker) they'll have the right value.

answered Aug 03 '12 at 18:52

fdiaz

2,600
21
27

score -1 · Answer 3 · edited May 23 '17 at 12:13

-1

I'm not sure what setting the timer to NULL does as opposed to setting it to nil, but I know that if you make a call on a nil object, it's a no-op. If you make a call on a NULL object, it think it crashes, though I haven't verified this. This post might help: NULL vs nil in Objective-C

edited May 23 '17 at 12:13

Community

1
1

answered Nov 06 '09 at 22:03

Matt Long

24,438
4
73
99

NSTimer crash with EXC_BAD_ACCESS on Iphone when invalidate

3 Answers3