- JS SDK
Third Party Product(s)
- Chrome browser
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
- Open chrome://media-internals.
- Add a video element with a stream as you normally would in an application.
- Observe new webMediaPlayer and its state as Play.
- Remove the video element.
- The webMediaPlayer's state will be paused. The correct state should be destroyed.
- Set the media element/node's srcObject to null before removing from the DOM. You can see a sample here.
- 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.
Third Party Reference
Please sign in to leave a comment.