Save state "floating wing window" not showing up when exiting back to the NES Classic menu

[sceptre2k3]

I posted this in the Hakchi2 repo, but am unsure whether it should go here instead (not quite certain which component has the error).

Original description:

"Background of my system:

hakchi2 2.15 + new retroarch clover (0.7)
have 283MB of games uploaded

I experience intermittent issues with the save state "floating wing window" not showing up when exiting back to the NES Classic menu.

What seems to be happening is when I go back to the NES Classic too quickly after the game loads (either on first load when selecting the game or when loading a save state), I end up back at the menu but there is no "floating wing window" to save or to resume the game. This is reproducible pretty much all the time for various retroarch systems (NES, Super NES, Genesis).

There is a workaround that seems present: I've tried this experiment by loading the game, waiting ~5-10s, then going back to the menu, and the "floating wing window" more consistently shows up.

I tested with the original 30 games (exit back to the menu as soon as the game loads), and the issue does not appear. This seems to indicate it is a retroarch-clover issue (new state zipping maybe?). Don't know if this is a (new) real issue, or something just inherent with the retroarch-clover design."

Additional information found after the initial post:

• the issue does not appear to be related to available memory, otherwise, it would fail all the time, and not just when exiting to the menu too quickly. I have also tested on my system using 245MB used, and the problem persists
• other users on gbatemp have reported the problem, so it is not specific to my system
• it is confirmed to exist in 2.14b and 2.15 (version I used). I do not know whether it was present in 2.13 and/or what retroarch-clover versions

[pcm720]

That's probably related (but not limited) to sleep in retroarch-clover script. Basically, you're leaving RetroArch too soon (most likely. it doesn't even initialize the core). Try not to do this.