Is it acceptable if I stop an app timer for dozens of times when the app timer is actually stopped. Will the memory leak if I operates in these scenario.Does it affect whether use scheduler when I init the app timer?
Is it acceptable if I stop an app timer for dozens of times when the app timer is actually stopped. Will the memory leak if I operates in these scenario.Does it affect whether use scheduler when I init the app timer?
Hi
I think the safer approach would be to maintain a state variable in your code, that you check before starting or stopping the timer. I quickly do not see the state checked internally.
It appears to occur when app_timers.c calls rtc1_stop() followed by rtc1_start(). I'm not able to get that code to execute from my application without hardcoding them to, but that is the sequence which causes the issue mentioned above. It must be some combination of events and timers which cause that code to execute.
It appears to occur when app_timers.c calls rtc1_stop() followed by rtc1_start(). I'm not able to get that code to execute from my application without hardcoding them to, but that is the sequence which causes the issue mentioned above. It must be some combination of events and timers which cause that code to execute.