fix(session): read the compressed client back when it is in front of a running game (#2600)

* fix(session): read the compressed client back when it is in front of a running game

* fix(session): keep the client compressed while focus is unknown

A missing or unreadable focus.json no longer counts as the client in front
of the game, so the readback timer starts only on a confirmed focus change.

* fix(session): invalidate focus snapshots after collection failures

* fix(session): retry focus snapshot publication
This commit is contained in:
MaxsTechReview authored and GitHub committed 2026-11-17 11:20:29 -05:00
1 parent 8e49dfe190
commit 8c8cae85cf
6 files changed
+221 -17

No files matched your search

+6
View File
@@ -20,6 +20,12 @@ retry delay, up to five minutes. After game exit, speculative launcher readback
until the session is under any explicit RAM cap, pressure has subsided, and available RAM
can cover twice the launcher's swap while leaving the headroom reserve. Normal demand paging
continues while readback is deferred; Steam does not have to wait for the monitor to recover.
The same readback runs while the game is still running once the client has been in front of it
for five seconds (a game stuck on a black screen and left through Steam, or a long stay in the
Steam menu), under the same memory checks and only without an explicit RAM cap. Missing or
unreadable focus data never counts as the client in front. Demand paging
alone left the Steam library and menus blank for about half a minute in that case. The
client is compressed again 20 seconds after the game is back in front.
Missing memory counters disable automatic pressure reclaim and speculative readback. Missing
PSI alone still permits the `MemAvailable` fallback. No root settings, swap sizes, compression
algorithms, Android process priorities or game-specific settings are changed.