Web Speech API and Chrome, stops working after a while until close out of chrome

[gene howell]

So I have a program that listens to the mic for long periods of time. After a while(it is different each time but usually after 5 minutes) the mic stops recognizing. It is not because of no speech detected or a sleep as I it is constant talking as well as I have recognition.start happening quite often. It seems to be an issue inside of chrome that just fails. Nothing in the the web tools shows an error. If I refresh it still does not turn on. I have to completely exit out of chrome then back in. If I set a window.open to a new chrome window(not tab) and then window.close on current tab it still does not work. I have to hit the red x then reopen. 

Any ideas? If this is a bug any ideas on how to close chrome first then reopen the page via code?

[PhistucK]

Sounds, indeed, like a bug (at least the part where you to have to exit Chrome for it to regain speech recognition abilities).

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

On Tue, Dec 22, 2015 at 5:47 PM, gene howell <ghow...@gmail.com> wrote:

So I have a program that listens to the mic for long periods of time. After a while(it is different each time but usually after 5 minutes) the mic stops recognizing. It is not because of no speech detected or a sleep as I it is constant talking as well as I have recognition.start happening quite often. It seems to be an issue inside of chrome that just fails. Nothing in the the web tools shows an error. If I refresh it still does not turn on. I have to completely exit out of chrome then back in. If I set a window.open to a new chrome window(not tab) and then window.close on current tab it still does not work. I have to hit the red x then reopen. 

Any ideas? If this is a bug any ideas on how to close chrome first then reopen the page via code?

--
You received this message because you are subscribed to the Google Groups "Chromium HTML5" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-html...@chromium.org.
To post to this group, send email to chromiu...@chromium.org.
Visit this group at https://groups.google.com/a/chromium.org/group/chromium-html5/.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[gene howell]

Thanks for the quick reply. I will give that a shot. Any idea on how I could do the close and open via code? It seems opening the new page whether a tab or a new window then closing the old one does not fix the issue. I have to manually close it then reopen. 

[PhistucK]

You cannot restart the browser using code.

☆PhistucK

[Fariz Kahfi]

Have you using button-triggered to play the recognizer?
when i clicked the button, the recognizer will starting to listen.
But when the recognizer is off, i'll just click the button again to play it.

[gene howell]

This is a custom application. There is a bug or a limit within the system that causes Chrome to stop recognizing or fail out and the only way to fix is to restart. 

 The temp fix is when the app fails I have it close chrome, I then wrote an application in C# that checks to see if chrome is running and if not restarts it. It works as a temp fix until the issue is resolved. Thanks.