You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the prepared stream, which contains the <InbandEventStream schemeIdUri="https://aomedia.org/emsg/ID3" value="0"/> field in the AdaptationSet, in the referenced player."
Take a Heap Snapshot and Analyze JsArrayBuffer
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 the InbandEventStream and InbandEventStream_asArray properties from the adaptation set object in DashManifestModel.js within the getRealAdaptations function, everything works as intended.
Memory usage when Adaptation Set contains InbandEventStream:
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 the JsArrayBuffer should remain stable or decrease as unneeded resources are freed.
The text was updated successfully, but these errors were encountered:
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.
I believe inband events should not have any duration that is longer than the containing segment. We should restrict it in MPEG to this. Also in case the event duration is longer than a segment, the event payload should be deleted on the client.
Events can legitimately be longer (e.g., duration of an ad break). They can appear before their presentation time.
I would rather do (maybe tunable) timeouts in the player.
Environment
https://6180c994cb835402.mediapackage.eu-west-1.amazonaws.com/out/v1/3f772c2a59824b9c9901ca513f605da9/index.mpd
If the stream is not available, please let me know so we can run it again.
Also I have added example of manifest that was crated with usage AWS Elemental MediaPackage
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.The text was updated successfully, but these errors were encountered: