tmewett
Game unexpectedly closes/aborts when locking screen
I have a Windows 11 machine. I had the game maximized and full screened. I played for a bit, locked my computer screen, then when I came back and unlocked the screen, I saw my browser, which was the window beneath the game. I pressed Alt+Tab to try go back to the game, but when I did, it actually showed that I had been on the game already, and that Alt+Tab actually made my browser come into focus, even though it had been visible the entire time. Then, when I pressed Alt+Tab again to bring the game into focus, the window just closed.
To get the game maximized, I used WindowsKey+Up, and then to get it Full-Screened, I used the + button. From there, I started up a new game, then went through the sequence of steps above. Nothing abnormal.
And when I start the game back up again, I see that there is a saved game, bringing me right back to where I was before the game unexpectedly closed.
Please let me know if more info is needed.
Do you get the same issue when you make it full-screen with the F11 keybind?
Sorry to have responded so late. Juggling emergencies.
Do you get the same issue when you make it full-screen with the F11 keybind?
Yes.
Btw, this is incredibly easy for me to reproduce. It is literally as follows.
- Start up the game. Don't even have to start a save, the main menu is good enough.
- Press F11 to go fullscreen.
- Lock the computer by pressing WindowsKey + L.
- Unlock the computer.
- Alt+Tab to the still open session of the game (which, weirdly enough, is not showing).
- The game appears to close abruptly upon completing the Alt+Tab.
Dies every single time if I follow the above steps on my Windows 11 laptop.
I can't reproduce this on Windows 10.
Technical notes: The issue may be caused by some subtle misuse of SDL resources or not properly handling window changes. Otherwise it may be a bug in SDL.
It wouldn't surprise me if this was a bug in SDL. The same issue has occurred for a few GUI libraries that I submit bugs for. Just wanted it documented to give other folks the chance to chime in and say me too.
Depending on how common the issue, it may make sense to escalate, or send out a stripped down build to see who else runs into the issue. For me, I think I can even get it to occur from the menu page.
I've had two people reproduce this, so it is a wider issue. No idea why it doesn't happen to me.
What GPU do you have?
Never mind; the two other repros have an Nvidia and an Intel integrated graphics, so it's not GPU vendor/driver related.
Here are my GPU details.
| Key | Value |
|---|---|
| Name | AMD Radeon(TM) Graphics |
| Adapter Type | AMD Radeon Graphics Processor (0x1506), Advanced Micro Devices, Inc. compatible |
| Adapter Description | AMD Radeon(TM) Graphics |
And this issue is still as easy to reproduce as it was originally.
If you want to send me a debug build, I am happy to run it on my machine. Maybe you can get some useful logs that way.