WebMediaPlayer memory leaks

Affects

Dolby Product(s)

• JS SDK

Third Party Product(s)

• Chrome browser

Description

When removing video or audio elements from the DOM without first destroying the webmediaplayer will pause the player and keep it in memory.

Your app may see performance issues if:

• your app has many users
• your app has many users that leave and join
• your app has users turn their video on and off repeatedly 
• your app does not use dolby voice, and your users repeatedly call stopAudio and startAudio

Reproduction Steps

1. Open chrome://media-internals.
2. Add a video element with a stream as you normally would in an application.
3. Observe new webMediaPlayer and its state as Play.
4. Remove the video element.
5. The webMediaPlayer's state will be paused. The correct state should be destroyed.

Workaround(s)

• Set the media element/node's srcObject to null before removing from the DOM. You can see a sample here. 

Action Plan

• The SDK will be updated to manage audio elements properly. However, since video elements are the sole responsibility of the developer, customers must test and update their applications accordingly.

Ticket References

Third Party Reference

• https://bugs.chromium.org/p/chromium/issues/detail?id=1232649

Dolby Reference

• CCU-222
• CCS-1927