Decide how long to watch for a store relaunch after a clean quit #256

Open
opened 2026-10-27 21:09:07 -05:00 by ethan-hann · 1 comment
Owner

Since #255, when the game's own program quits with exit code 0 inside the 30 s relaunch window, the session ends two process-list looks (about 4 s) later instead of after the 2-minute grace (D13.10). That fixed Balatro, which was held up for two minutes after a quick quit. A game that relaunches itself through its store and exits with code 0 now gets only those 4 s for the new copy to appear; if the store is slower, the after-play choices show early, and the after-play guard (D67.5) refuses a snapshot while the game runs (Choose again).

Check real games on Steam, GOG and Epic that relaunch through their store, note their exit code and how long the new copy takes to appear, and decide whether the 4 s is enough or should be longer (for example 10 s) for a clean exit. Also confirm Balatro's exit code on Windows (the log now records it).

Since #255, when the game's own program quits with exit code 0 inside the 30 s relaunch window, the session ends two process-list looks (about 4 s) later instead of after the 2-minute grace (D13.10). That fixed Balatro, which was held up for two minutes after a quick quit. A game that relaunches itself through its store and exits with code 0 now gets only those 4 s for the new copy to appear; if the store is slower, the after-play choices show early, and the after-play guard (D67.5) refuses a snapshot while the game runs (Choose again). Check real games on Steam, GOG and Epic that relaunch through their store, note their exit code and how long the new copy takes to appear, and decide whether the 4 s is enough or should be longer (for example 10 s) for a clean exit. Also confirm Balatro's exit code on Windows (the log now records it).
ethan-hann added this to the 1.0 milestone 2026-10-27 21:09:07 -05:00
Author
Owner

0.9.21 narrowed the clean-quit rule: the short wait applies only after the program ran for at least 10 seconds (CleanQuitMinimumRun); a clean exit sooner is treated as a relaunch stub and keeps the full grace (D13.10). The real-store check in this issue should confirm 10 seconds is right.

0.9.21 narrowed the clean-quit rule: the short wait applies only after the program ran for at least 10 seconds (CleanQuitMinimumRun); a clean exit sooner is treated as a relaunch stub and keeps the full grace (D13.10). The real-store check in this issue should confirm 10 seconds is right.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ethan-hann/SavePoint#256
No description provided.