-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WPE 2.38: OOM(Out of Memory) error with HLS and DASH playback while streaming any content with WebInspector open #1446
Comments
Unfortunately, I don't have access to PlutoTV and ITVX App so I cannot test them, so I focus on MVT tests. I found that in the case of Shaka tests, each test creates a new "video" element, and in theory, the existing one from the previous test is removed. Nevertheless, after adding some logs, I discovered that the "video" element from the previous test was not removed completely (probably shaka keeps some reference to it), which caused it to be kept in memory. It works as expected in the case of "DashJS tests" and "Progressive HTML5 tests". @hridhya-narayanan-infosys : Can you run PlutoTV or/and ITVX with |
@pgorszkowski-igalia should I need to share logs with including the downstream patch changes 39f3e68 which is shared as part of #1335 ? |
@pgorszkowski-igalia Below are the logs from Sagemcom VA for PlutoTV and ITVX app with enabling WEBKIT_DEBUG=Media,MemoryPressure. |
From your logs I see that you have 200MB set as threshold for memory pressure which is rather small value. Keep in mind that if you use RWI it will gather additional 200MB of data at least for network data kept for RWI.
As a consequence of low memory threshold value, you exceed it quickly (even more quickly with RWI). |
@hridhya-narayanan-infosys : do you know what js library is used for adaptive media playback in plutotv and itvx? I am investigating MVT frameworks and it seems that in case of shaka player tests, the old media element is not removed by GC because something keeps reference on the old media element (video element from the previous test). The consequence of this is that memory usage is greater because of the data from the old video elements which are not removed even after GC. |
@pgorszkowski-igalia , Below are the details which I got from webinspector page. For Pluto TV app, I could see for HLS playback it uses [email protected] and for DASH it uses dash.all.min.js
|
We are seeing Out of memory error with HLS and DASH playback when streaming any content with webinspector open. We could see the memory max usage increases and then finally WebKitBrowser Plugin gets deactivated due to reason Memory Exceeded.
Below are the observations on Sagemcom VA device while streaming the content with webinspector open:
Scenario to reproduce:
Below are the logs from Sagemcom VA for DASH and HLS playbacks:
Pluto TV (https://app-virginmedia360.pluto.tv/) HLS playback:
wpeframework.log
ITVX App (https://app.10ft.itv.com/3.449.2/virginmedia) DASH playback:
wpeframework.log
The text was updated successfully, but these errors were encountered: