Open grand719 opened 2 weeks ago
After further investigation, I managed to find out that the issue occurs due to the event_duration being set to 40 hours in IsoBox - emsg. How should this situation be approached, and how should the player react in such a case? We also managed to remove the emsg IsoBox using AWS MediaLive, but I believe the player should also have logic in place to prevent behavior like overloading the memory when events are too long.
Environment
Steps to reproduce
<InbandEventStream schemeIdUri="https://aomedia.org/emsg/ID3" value="0"/>
field in theAdaptationSet
, in the referenced player."Observed behavior
In the taken snapshot, we can observe that the JsArrayBuffer is consistently increasing, and the memory usage is not dropping. During the debug session, I noticed that unusual memory management behavior is caused by the
<InbandEventStream schemeIdUri="https://aomedia.org/emsg/ID3" value="0"/>
element, which is added to the video AdaptationSet. Additionally, after deleting theInbandEventStream
andInbandEventStream_asArray
properties from the adaptation set object inDashManifestModel.js
within thegetRealAdaptations
function, everything works as intended.Memory usage when Adaptation Set contains InbandEventStream:
Manifest
Expected behavior
There should be no memory leaks when playing a live stream, even with
InbandEventStream
set in the AdaptationSet. Memory should be released correctly, and the size of theJsArrayBuffer
should remain stable or decrease as unneeded resources are freed.