alexa / alexa-smart-screen-sdk

⛔️ DEPRECATED Active at https://github.com/alexa/avs-device-sdk
Apache License 2.0
76 stars 26 forks source link

The GUI page got too many web audio objects ,then stuck #126

Closed Jinglouyan closed 2 years ago

Jinglouyan commented 2 years ago

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.

Briefly summarize your issue:

When I say "tell me a joke", the GUI page show a joke with playback. Then I use the chrome devtool to analysis to see the memery , the count of web AudioContext and web AudioDestinationNode are increasing every time. After about 1,000 times , the GUI page got stuck. image image image

What is the expected behavior?

The web audio objects should be released after used,do not increase every time .The GUI page should works well ,even after 1,000 times.

What behavior are you observing?

Web audio object were not be released

Provide the steps to reproduce the issue, if applicable:

say "tell me a joke" , and duplicate

Tell us about your environment:

What version of the AVS Device SDK are you using?

  <2.8.0>

Tell us what hardware you're using:

Tell us about your OS (Type & version):

Have you tried the same use case with AVS Device SDK SampleApp?

More information

alexa smart screen sdk : 2.8.0 apl-client-library:1.7.2 apl-core-library:1.7.1 avs-device-sdk:1.25.0

Jinglouyan commented 2 years ago

@powj If it do have problems , what could I do to remedy it without change version without changing version Looking forward to your reply , thanks.

powj commented 2 years ago

Hi @Jinglouyan , thank you for providing the reproduction steps.

After investigating I believe that the problem is coming from the apl-client-js library which we depend on for rendering APL. It occurs specifically with 'tell me joke' because this utilizes APL SpeakItem which is rendering audio through the browser. I have brought this to the attention of that team, however at the moment I am unable to provide any workarounds as further investigation is needed to understand root cause the issue.

Jinglouyan commented 2 years ago

@powj Thanks for your reply, I will continue to focus on this issue.