Hi @tzongw, I don't see where this creates a problem. If moduleTimerHandler returns with AE_NOMORE then aeTimer != -1 indeed but it also implies that Timers have no elements. Therefore, the next call to RM_CreateTimer will always end up adding the first entry and therefore deleting and reinstalling the timer.

Yes, no running problem here, but it's problem prone. Imaging ae changes it's implementation, timer id is unique only when it's valid(or say timer id is reusing), just like RM_CreateTimer. Deleting a dangle timer id means you may delete another timer by mistake.