-
-
Notifications
You must be signed in to change notification settings - Fork 888
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
Resizing window will casuse high vmem usage without mem release #7362
Comments
shrink.mp4Reproducible with windows resize |
an you try installing |
It is tested using the -git version. $ yay -Qs egl
local/egl-wayland-git 1.1.15.r1.gf30cb0e-1
EGLStream-based Wayland external platform (git version) |
AMD, can't repro. Nvidia issue? |
Probably, let me try my intel gpu |
PROBABLY a bug introduced in nvidia beta (560). After downgrading to 555.58, this issue can't be reproduced now. Closed this issue for now? |
yes should be closed as it is not a Hyprland issue |
For other fellows that went into the same issue after updating to NVIDIA 560, here are some reference for you to track: |
Please see the latest update here for a suggested workaround: |
Regression?
No
System Info and Version
System/Version info
Description
After toggling
fullscreen 0
dispatcher for Telegram Desktop, the vmem usage is constantly increasing, and the memory won't release when the application was exited.How to reproduce
Open telegram desktop (latest from Arch Linux repository, flatpak version not tested), open nvtop, toggle
fullscreen 0
multiple time, and experimenters will see the GPU memory usage for Hyprland is increasing. Kill telegram desktop window, and the memory is keeping the same. Exit the telegram desktop process, the memory is still not released.[Update]
This issue is also reproducible on Firefox. Toggle floating mode on the window, then keep toggling the fullscreen mode, the vmem usage will also keep increase without release.
Crash reports, logs, images, videos
hyprland-high-vmem.log
The text was updated successfully, but these errors were encountered: