Hi Joe, can you please give an example of exactly how you call speechSynthesis.speak()? It'd be helpful to know what parameters you are passing. For example, if you sometimes specify a language or a voice name, but not always, this behavior could occur.

@Joe: Could you please respond to comment# 3.

Thanks!

Yep, I’ll have something put together this weekend to demonstrate how the issue arises. Thanks so much for the quick follow up!

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This past weekend I did some extensive testing to try and replicate the issue on demand. For better or worse, the issue never presented itself once during this time. Testing was done on the same machine that presented the issue all last week, without any updates or changes in software. At this point I'll consider it an anomaly.

The flow I use to trigger the TTS is as follows:
-Start of app: call voice list, set voice name, rate, pitch, language.
-On TTS calls: stop speech, call voice name, rate, pitch, language; speak utterance.

I do call all voice parameters with each TTS utterance.

I am unsure what could have changed during this time but the issue no longer seems present. I was able to screen capture the issue happening before. I use the TTS feature extensively with educational application for visually impaired students. As such, I usually have daily usage and will continue will continue to monitor and create a fresh bug report if it happens again.

The quick and thorough feedback from the Chromium team was amazing to witness firsthand. You guys are great!

Thanks Joe for looking into it further! I'm going to close this, but please re-open if you notice it happening again.