Skip to content
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] Memory leak during video playback on i.MX6DL #1191

Open
vnd opened this issue Sep 21, 2023 · 1 comment
Open

[wpe-2.38] Memory leak during video playback on i.MX6DL #1191

vnd opened this issue Sep 21, 2023 · 1 comment
Labels

Comments

@vnd
Copy link

vnd commented Sep 21, 2023

I'm trying to play 3 short videos (~2-3 seconds each) in a loop on an i.MX6DL board, running Yocto image (dunfell).

wpewebkit 2.38.3
cog 0.14.1
gstreamer 1.16.3
IMX_DEFAULT_BSP = "mainline"
wpebackend-fdo

Simple HTML page is playing 3 videos in a loop:
https://gist.github.com/vnd/88449eb6fb6d688bc6f4882f18b2736e

WPEWebProcess RssAnon memory is growing with a speed of about 0.7MiB/minute, and eventually OOM killer kicks in.

The only caveat of the above example is that for some reason every couple of playbacks 'ended' event is not fired, and so I've added a timeout for resuming playback. Not sure if it could be causing the leak, but either way there's a bug somewhere.
Note: this page is a minimal reproducible example, production UI leaks 2-3 times faster.

Apart from hopefully fixing the leak, even slowing it down could help. Also I'm genuinely curious in all relevant info, in particular what is leaking: wpewebkit, gstreamer plugins, kernel or cog?

@vnd
Copy link
Author

vnd commented Sep 22, 2023

Upon further testing, leak is happening upon loading videos, and not during playback itself. Since we have a bit edgy use case with very short videos (~3 seconds) being played repeatedly, it resulted in a big memory leak. Hopefully UI guys can just switch to a longer videos, then the leak will be negligible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants