This is a tracking bug.

Version

master, not on production yet.

Describe the bug

When the user keep spamming the microphone button, the engine may stop. Requires F5 to resume.

Steps to reproduce

1. Open 06.i.direct-line-speech sample
2. Click on microphone button
3. While it is recording, keep spamming the button and say "Testing"
4. Keep spamming the button for extended time after recognition
5. After recognition, it should turn on microphone again to record for the second utterance

Expected behavior

It should start recording for the second utterance.

Instead, it stop recording and went into a locked state.

Additional context

[Bug]