Headless monitor leads to memory leak to ludicrous amounts, then crash if peaked or removed, sunshine might be involved #11693
Unanswered
irabrine
asked this question in
Bugs - Performance
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hyprland version
Hyprland 0.51.0 built from branch at commit 46174f7 (version: bump to 0.51.0).
Date: Wed Sep 10 12:41:05 2025
Tag: v0.51.0, commits: 6418
built against:
aquamarine 0.9.4
hyprlang 0.6.3
hyprutils 0.8.4
hyprcursor 0.1.13
hyprgraphics 0.1.5
no flags were set
Regression
can't call it a regression since i didn't use it before this version, and can't test since usecase requires this version for sunshine
Describe the bug
memory leak from having a headless monitor, it steadily keeps getting more and more ram over time
using the headless monitor makes the hyprland process use a tad bit more cpu which is expected, but it also makes the growing amounts of memory be faster than just using main screen
after a while (vague, i know, i noticed it's once it's over a gig of ram) when i disconnect the stream with sunshine, hyprland entirely freezes, and even locks me out of moving to tty2, only way i recover is by ssh and kill hyprland from btop, which unfortunately means i get no crash report
also when i peak my ram, when my usage gets to around 30.9g sys total, hyprland encroaches a bit too much and leads to a frozen system, no ssh saves that one
there was a similar issues with #9611 but my hyprcursor is up to date
i think it takes about 2 hours to get to 1 gig, 4g is average by the end of the day, i experimented once and didn't close it for a few days and it went up to 9g and kept going, had to reset since i need my ram back
Reproduction steps
System info and config
Beta Was this translation helpful? Give feedback.
All reactions