hold_key_count is the cause, even if it did overflow it would just continue incrementing it. my feeling is that this has something to do with timers. i thought perhaps the timer generating events for
handler_keyTimer becomes corrupted but it also processes the front button presses and sounds like it still responds to that when keyboard and metro crash.
there is a separate timer however used to generate events for
handler_HidTimer, maybe it becomes corrupted somehow, and the metro timer as well?
i wonder if
ticksRemain overflows when it's decremented, i don't see how it's possible but who knows, maybe there is some weird race condition... one way to prevent it would be to check if it's greater than
ticks after this line:
@sam could you give this a try? if this is indeed what happens it would result in the timer set to a really long delay which would explain the behaviour...
i really like the idea of separating critical events into their own queue.