-
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: Out of memory error while streaming any content with WebInspector open #1335
Comments
Below is an additional observation made by making the JSC_criticalGCMemoryThreshold=0.10 . With this change, the playback was running for almost 45 mins. In this, for the first 30 mins the memory increase was stable. But after 30 mins, the memory increase is very fast. Image tested: root@raspberrypi4-64-rdk-android-mc:~# cat /version.txt |
Could you please test with latest wpe-2.38 ? I landed several build fixes. |
thanks @calvaris , |
Yes, all patches merged during merge commit 0cb500e . |
I have pulled the latest wpe-2.38 code and tested the scenario on RPI4 device. Observation
From Controller UI console I could see below logs:
logs: Without webinspector open I could see memory usage(/sys/fs/cgroup/memory/memory.max_usage_in_bytes) is around 461193216 after 40 mins of CNN playback Image tested:
|
Any update on this issue? |
@hridhya-narayanan-infosys : I am able to reproduce the problem and I am investigating the reason of the problem. |
@hridhya-narayanan-infosys : the problem is also visible in upstream (in specific situation). I created a fix in upstream: WebKit/WebKit#37536 which is waiting for review and merge. |
@hridhya-narayanan-infosys : The downstream patch you can find here: 39f3e68, please use it and test. |
@pgorszkowski-igalia thanks. I will test the issue with above patch. |
@pgorszkowski-igalia , I have tested the issue with above patch on RPI 4 device. I could see good improvements. Currently checking on the behaviour with other apps as well. |
Tested PlutoTV App(https://app-virginmedia360.pluto.tv/) on RPI4 device and we could observe crash around 30 mins. Testing with other apps is in progress. |
@hridhya-narayanan-infosys : the crash is because of exceeding the memory limit? |
BTW: CNN app is unavailable, I use link: https://widgets.metrological.com/lightning/liberty/2e3c4fc22f0d35e3eb7fdb47eb7d4658#app:com.metrological.app.CNN, on RPi it hangs on CNN logo. |
yes the crash is due to memory exceeded. From logs I could see below:
Attached logs: |
With https://app-virginmedia360.pluto.tv/ I get "We're having some trouble... We're currently working on this issue. Please reload the Pluto TV app." , but reloading gives the same result:( |
From your logs I see that the memory usage is huge at the beginning, are logs from the last phase of problem? In further logs I see that you use AAMP-PLAYER for video playback - AAMP-PLAYER is something separate than WPE (it is a separate lib). Does the problem occur with or without this AAMP-PLAYER? |
Regarding the logs, yes those are the logs from last phase before the crash. We didn't use AAMP player. |
There are a lot of logs with:
Are you sure that PlutoTV does not use it? via UVE js bindings? Do you know what kind of playback is used by PlutoTV? regular one or adaptive (mpeg-dash or hls)? |
In the earlier logs shared we had opened a HTML5 app(Xumo) which used AAMP JS bindings before launching PlutoTV app. So the log was showing the AAMP-PLAYER related logs. Pluto TV App has been tested once again. These are the logs. PlutoTV App uses HLS playback and also from JS code of PlutoTV App I couldn't see usage of Aamp player UVE APIs. |
Do you observe similar behaviour in other apps which use HLS? |
In RPi, there is a significant increase in memory consumption of WPEThunder when Webinspector is started along with the streaming of any content. But no crash is seen because there is no limit set for WPEThunder and We were able to stream for more than 1.5 hours. But, the memory max usage rapidly increases. Below are the observations in RPi.
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.limit_in_bytes
9223372036854771712
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
531464192
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
544538624
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
550207488
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
561790976
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
584716288
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
620036096
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
635936768
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
646520832
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
655519744
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
695853056
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
702447616
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
711151616
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
721469440
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
737206272
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
835309568
root@raspberrypi4-64-rdk-android-mc:/sys/fs/cgroup/memory# cat memory.max_usage_in_bytes
838696960
Every memory usage values are noted within 1-2 mins.
Scenario to reproduce
The text was updated successfully, but these errors were encountered: