-
-
Notifications
You must be signed in to change notification settings - Fork 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
Idle games in background are not getting enough CPU time #7262
Comments
hyprland doesn't control cpu times |
Should I raise this in aquamarine? It's certainly possible to send frame callbacks to apps so they are not getting CPU throttled. |
if you want frame callbacks to be sent then say that, because that's already reported and this would be a dupe. Search the issue tracker. |
I just learned what's needed from the KDE devs a few hours ago, otherwise I would have stated this earlier of course. |
fixed with #7582 |
Regression?
No
System Info and Version
System/Version info
Description
I have an idle game running and I tested with others. (Unnamed Space Idle or Realm Grinder)
Both games in the background/different workspace are not getting enough CPU time so the timers start to drift. When 30 realtime seconds occur only ~3-4 seconds are registered in the game.
As I'm also running KDE in X11 I noticed that this must be a Wayland compositor problem. Whereas in KDE X11, the game are running fine in the background, they have the same behaviour in KDE Wayland. Easily verifiable in
htop
with looking at theTime+
data.Now that Hyprland has its own Wayland compositor, is there a chance to add some option so selective games/apps are not getting throttled and have the same priority as being in the foreground?
As a workaround I tried
gamescope
and while it's indeed able to run un-throttled in the background, after some time it just closes/crashes and I haven't found out why. Not getting the crashes in KDE.How to reproduce
Play Realm Grinder or Unnamed Space Idle.
Have them in foreground, check the timer.
Put them in background, wait 30 seconds.
Put them in foreground again, only ~3-4 seconds of the in-game timer has passed.
Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered: