-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Memory leak when viewing mpv fullscreen #4662
Comments
Instead of |
Another evidence of a leak is that when the video is fullscreen something like this:
shows the number of allocated framebuffers climbing rapidly (100 more in a few seconds). |
I think this bug is related to this line
After importing the buffer we never destroy it. The |
There seems to be something specific to how mpv is handling fullscreen that triggers the bug. Fullscreen youtube videos in Firefox don't seem to cause the same issue. I'm using the latest mpv release (0.29.1) as packaged by Ubuntu 19.04. |
We need to destroy the gbm_bo we imported and drmModeRmFb. Closes: swaywm/sway#4662
Can you try swaywm/wlroots#1872? |
@emersion from 5 minutes of testing that seems to fix it, thanks. I'm now running that patched version and will keep monitoring to see if there's anything else. |
We need to destroy the gbm_bo we imported and drmModeRmFb. Closes: swaywm/sway#4662
We need to destroy the gbm_bo we imported and drmModeRmFb. Closes: swaywm/sway#4662
We need to destroy the gbm_bo we imported and drmModeRmFb. Closes: swaywm/sway#4662
We need to destroy the gbm_bo we imported and drmModeRmFb. Closes: swaywm/sway#4662
We need to destroy the gbm_bo we imported and drmModeRmFb. Closes: swaywm/sway#4662
We need to destroy the gbm_bo we imported and drmModeRmFb. Closes: swaywm/sway#4662
Either sway or mpv are doing something wrong when fullscreen that results in memory being unreclaimed in the kernel. Only killing sway returns the memory to use. Here's how to reproduce:
Killing mpv does not reclaim the memory but killing sway does. Running mpv with
gpu-context=waylandvk
seems to fix it or at least reduce it very significantly. I get video tearing with that option though.At least on my system I can reproduce this at will right now so I can gather more info if wanted.
The text was updated successfully, but these errors were encountered: