For some reason, sometimes when I close a game I’m currently playing, by pressing F1 -> Close Content, RetroArch closes itself. On very rare occasions, it won’t close itself but most of the times, it does.
Is there a way to resolve this somehow?
1 Like
We would need to see a log of it doing so to determine whether it’s crashing or closing itself “cleanly”.
Where can I see them?
here’s a guide for generating and posting a log: https://docs.libretro.com/guides/generating-retroarch-logs/
Okay I think I figured it out, it has to do with achievements. If I play a game that has no record in RetroAchievements, I can close it fine and RetroArch doesn’t crash. For the games that DO have achievements, if I turn off achievements altogether, the problem stops happening.
1 Like
Ah, are you using the version from the Play Store? If so, it hasn’t been updated in 2+ yrs (Google won’t let us due to a requirement to support their “scoped storage” API).
I recommend sideloading the APK from our website, instead.
This is posted in the Windows subsection 
I’m on 1.16.0
Also the Reddit thread I linked to was started some months ago so this is a recent-ish thing I think
Sorry, I answer like 60+ questions per day across like a dozen common platforms (and other oddballs). The reddit thread from 9 months wouldn’t have been unusual for an Android issue, as we keep getting reports about old, zombie issues, since the Play Store version hasn’t been updated in a long time.
In any event, if it’s the thing from the github issue, it sounds like it’s at least been mitigated. If something is still going on, it may not be directly related beyond just the symptoms. I guess we’ll need to get a backtrace from a debug build of RetroArch.
1 Like