Botframework-webchat: Cognitive Speech Services sample throws a runtime error in Chrome

Created on 27 Mar 2019 · 11Comments · Source: microsoft/BotFramework-WebChat

I was unable to reproduce this issue in Edge or Firefox

Reproductions steps:

Navigate to 06.c.cognitive-services-speech-services-js in Chrome version 73.0.3683.86
Open console
Press microphone button and say 'Help'
Notice console errors regarding AudioNode, pasted below

We are still investigating the cause of this bug. Please feel free to add a +1 and the details of your experience to this issue.

Notes:

Does not repro with speech web-browser sample.

Speech Bug P1 Sample front-burner

Source

corinagum

All 11 comments

In my case, it is the error as the image below
error

xiaolangxyz on 27 Mar 2019

@xiaolangxyz looks like your problem is related to #1823.

compulim on 28 Mar 2019

On the other hand, https://webchat-playground.azurewebsites.net/ works, while 06.c also fails on my box. Both of them connect to Cognitive Service.

compulim on 2 Apr 2019

Maybe Chrome updated the error message.

Connecting nodes after the context has been closed is not useful.

compulim on 21 May 2019

👍1

@compulim are we reassigning this one to you?

corinagum on 21 May 2019

Took this now.

compulim on 22 May 2019

Today, we have a workaround for this particular Chrome bug:

Speak an utterance
Cancel in the midway
Speak another utterance

Expected: speaking is falsy, then turn to truthy, then receive "start" event, and audio is played
Actual: speaking is falsy, then turn to truthy (which is wrong), but receive no "start" event, and no audio is played

Our workaround is, if we did not receive "start" event within a second, we will cancel and restart, up to 2 times.

Since this workaround applies to both Chrome and non-Chrome (Cognitive Services), thus, if Cognitive Services took more than 1 second to fetch/decode the audio, we would think it is bugged and we restart it. Leading to some long text to fail synthesizing.

I tested Chrome 74 and Edge "Anaheim" 76 and seems this bug no longer repro. Will try more browsers and if still not repro-ing, will remove this workaround. And next time, we shouldn't applies a workaround too broad, we should limit the workaround by building a new polyfill instead.

I am using the HTML below, then repetitively click "Speak" and "Cancel" button.

<!DOCTYPE html>
<html lang="en-US">
  <head>
    <title>Speech</title>
  </head>
  <body>
    <button class="speak">Speak</button>
    <button class="cancel">Cancel</button>
    <p class="pending">Pending: <span class="value"></span></p>
    <p class="speaking">Speaking: <span class="value"></span></p>
    <script>
      document.querySelector('button.speak').addEventListener('click', () => {
        speechSynthesis.speak(new SpeechSynthesisUtterance('A quick brown fox jumped over the lazy dogs.'));
      });

      document.querySelector('button.cancel').addEventListener('click', () => {
        speechSynthesis.cancel();
      });

      setInterval(() => {
        document.querySelector('.pending > .value').innerHTML = speechSynthesis.pending + '';
        document.querySelector('.speaking > .value').innerHTML = speechSynthesis.speaking + '';
      }, 100);
    </script>
  </body>
</html>

compulim on 25 May 2019

👍1

In order to verify the fix:

Ask the bot to synthesize a very long text that took > 1s to download the MP3 file from Cognitive Services
Verify F12 that we don't see the "audio node is disconnected" error nomatter how long the text is

compulim on 12 Jun 2019

Fix is verified in #2035. It will be officially released for 4.5 in July. If you need this fix immediately, please build master into a locally hosted version of Web Chat.

corinagum on 14 Jun 2019

Hi, I am still getting this same issue in chrome 77.

Also, after this, the speech recognizer is not starting.

I am manually canceling the voice since I need to stop it once user presses a button, after that this issue is happening.

Is it a known bug?

alokraj68 on 14 Oct 2019

@alokraj68 Thank you for bringing this to our attention. I am going to file another issue since this appears to be a slightly different bug. https://github.com/microsoft/BotFramework-WebChat/issues/2469

corinagum on 14 Oct 2019

Was this page helpful?

0 / 5 - 0 ratings