Crash when Windows resumes from suspension

JosefNemec / Playnite

Video game library manager with support for wide range of 3rd party libraries and game emulation support, providing one unified interface for your games.

https://playnite.link

MIT License

9.15k stars 494 forks source link

Crash when Windows resumes from suspension #3731

Closed BrutuZ closed 5 months ago

BrutuZ commented 5 months ago

Bug Description

Playnite crashes when Windows resumes from suspension mode (S3 Power State).

To Reproduce

Launch Playnite
- From cold boot: Playnite.DesktopApp.exe --uridata "playnite://playnite/start/7824d16e-5261-41b5-8a53-b595825717b5" --hidesplashscreen --startclosedtotray
- Everything works as intended so far, game is launched, Playnite is ready on the taskbar afterwards.
Have Windows go into suspension via idle timer
- Turn off Screen after 1 minute | Turn off Hard Disk after 20 minutes | Go to sleep after 2 hours
Wake the system
Try to open Playnite via the tray icon and watch it vanish on hover because the application crashed

Diagnostics ID

28a9727a-87a1-4ba1-a7c7-cc7dcb32c1b5

Screenshots

No response

JosefNemec commented 5 months ago

Can't reproduce. Does it happen when running Playnite in safe mode (main menu -> help -> restart in safe mode)?

BrutuZ commented 5 months ago

I don't normally run Playnite in safe mode, it happens when launched with the steps described as I run that daily via Scheduled Tasks.

It doesn't appear to crash when I wake the system right after suspension, but if I stay away for several hours the tray icon will vanish when I hover it and using a desktop shortcut to a game will launch Playnite from scratch, splash screen and all.

JosefNemec commented 5 months ago

Add --safestartup to those startup arguments and try to reproduce the issue. If it doesn't occur, then it's some addon causing the issue. If it still happens, then no idea. I can't think of anything in Playnite itself that could be causing this.

JosefNemec commented 5 months ago

Also since Playnite just terminates without any crash dialog (or crash info in the logs), it means the crash is not happening anywhere in our code (that would result in crash handler dialog). So I literately don't have anything to go by here if I wanted to debug this. It's most likely crash caused by some 3rd party (addon, app, driver or weird system config).

BrutuZ commented 5 months ago

It happened again today (just powered on the PC, the Scheduled Task triggered soon after, I closed the game after some 15 minutes and left the system alone until it went to sleep), but not when I tried to deliberately trigger it last time with manual suspension or shorter intervals and regular client launches.

It's a weird and inconsistent crash, since it's killed in its sleep without leaving any log trace I didn't really have high hopes on debugging it. Opened the issue in case the few clues might hint to something but doesn't seem to be the case so I'll just cope.

BrutuZ commented 3 months ago

In the off-chance someone runs into this issue, I think I found out the actual reason and it had nothing to do with Playnite, but actually just a couple of Scheduled Task settings.