https://devzone.nordicsemi.com/f/nordic-q-a/3203/race-condition-in-app_timerI&#39;ve been looking at the app_timer source after an odd lockup I had. I think it has a race condition in it. The code which adds events to the pending events list is usually called from user code. It mutates the list of events and then calls timer_list_handle_scheden-USTelligent Community 13Fri, 05 Sep 2014 18:06:53 GMThttps://devzone.nordicsemi.com/thread/11785?ContentTypeID=1Fri, 05 Sep 2014 18:06:53 GMT137ad170-7792-4731-bb38-c0d22fbe4515:507728b7-e0bd-4f12-8ce9-859dd305e251Rick Bronson<p>Not sure if this is the same problem I&#39;m seeing. I have 6 timers with tick timeouts of 2000, 1000, 5000, 100, 5000, 30000. The 1000 one sometimes gets called twice in a row with no delay. If I change it to 999, it seems to work fine. Seems like a race condition to me. See <a href="http://members.efn.org/~rick/pub/main.c">members.efn.org/.../main.c</a></p><div style="clear:both;"></div>