X11: Handle WM_STATE transitions to detect Withdrawn/Iconic states #14770
+32
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When running SDL3 applications on tiling window managers like i3, moving a window to an invisible workspace does not trigger
SDL_WINDOW_MINIMIZEDorSDL_WINDOW_HIDDEN. Consequently, the application continues rendering at full speed (VSync dependent), consuming unnecessary GPU/CPU resources even when not visible.When a workspace is hidden, i3(and possible other tiling WMs) unmaps the container and sets the client window state to
WithdrawnState(via theWM_STATEatom). Previously, the SDL3 X11 backend ignored changes toWM_STATEduringPropertyNotifyevents, failing to detect this transition.I provide a test program to log window flags and FPS:
Details
Before fix:
After fix:
Existing Issue(s)
I'm sure I've seen somewhere that people are complaining about games on i3wm hogging the CPU/GPU in the background, but I can't find it now.