You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hyprland leaks VRAM when moving the mouse between displays until it gets stuck at ~2750MiB when hyprpanel is running.
It increases 10MiB if I move to the display on the left, and 30MiB on the one to the right.
The VRAM doesn't seem to be freed upon closing the program.
To Reproduce
Start Hyprpanel and move your mouse from one display to another
Expected behavior
GPU VRAM stays constant
Screenshots
Sorry for the yt link github doesn't let me upload the video for some reasons. Video Demonstration
Desktop (please complete the following information):
Nixos
Hyprland 0.47.0
Nvidia 3090 with 565.77 drivers
Both display are 1080p
Additional context
This doesn't happen when switching workspace on the same display.
This doesn't happen without hyprpanel.
The culprit might very well be nixos / nvidia / hyprland / my hyperpanel config.
The text was updated successfully, but these errors were encountered:
Tried on a clean config. It seems to be an astal issue.
Each time a widget is rendered, the vram is not released when it's destroyed.
The display switching creates a new osd each time.
Describe the bug
Hyprland leaks VRAM when moving the mouse between displays until it gets stuck at ~2750MiB when hyprpanel is running.
It increases 10MiB if I move to the display on the left, and 30MiB on the one to the right.
The VRAM doesn't seem to be freed upon closing the program.
To Reproduce
Expected behavior
Screenshots
Sorry for the yt link github doesn't let me upload the video for some reasons.
Video Demonstration
Desktop (please complete the following information):
Additional context
This doesn't happen when switching workspace on the same display.
This doesn't happen without hyprpanel.
The culprit might very well be nixos / nvidia / hyprland / my hyperpanel config.
The text was updated successfully, but these errors were encountered: