-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recognizer becomes weird after cancellation #123
Comments
@timobaumann Do you have the time to look into this? If the students notice this in their dialog development work (as in #125), less experienced users would probably struggle with it even more. |
it's also possible to trigger this without clicking try:
|
interesting: when I wait a while after that, I get:
too bad we don't know what that thread is that is failing. |
Wow, that's a weird exception. The Google search seems to indicate that this is somehow related to audio playback. Are we playing back audio in some way before/during/after running the recognizer? |
nope. but I got that only once, so would not read too much into it. |
Thanks! |
the main fix is in sphinx.frontend.feature.LiveCMN : avoid to keep stale Data objects around in the queue. Other changes: (a) avoid re-running recognition after cancellation (Sphinx.java) (b) Java-9 adaptations in many places
I still wonder why this bug only occurred on the very first invocation (i.e., you could cancel on a later invocation if you said something in the first without breaking things). Oh well. |
Wow. Cool. Thanks for taking care of this! |
Sometimes, I observe the following behavior:
This doesn't seem entirely reproducible, but we should keep an eye on it and fix it.
The text was updated successfully, but these errors were encountered: