Closed i30817 closed 4 years ago
Threaded video setting in retroarch does not influence these. Or at least not completely, i was able to savestate once, but subsequent tries froze again.
This might be a Retroarch problem, i'm bisecting retroarch after noticing that even going back 1-2 years in ppsspp didn't change things.
Edit: no it isn't. It's https://github.com/hrydgard/ppsspp/issues/11429 but the hack stopped working for some reason. No wonder the break of the hangs sent me to the mutex that the 'bandaid' commit for that issue introduced.
Description
Self built retroarch from upstream; with make (not cmake which doesn't work right now). It crashes whenever you try to save, reset or close the core (and probably other things). Using gdb with a build with DEBUG=1 and ctrl+c during the 'pause' it shows it's at a mutex wait on the emulation thread pause.
Expected behavior
Not crash or freeze I guess.
Actual behavior
Freezes and crashes.
here is a freeze on savestate:
here is a crash on restart core - it's not useful, except for the name of the stopped thread. I had to restart twice for this to happen in the debug build.
Steps to reproduce the bug
Just load any game on the core and try to savestate from the menu (freeze), or reset (crash), or close the core (freeze).
Bisect Results
No clue, the core only recently started to work again for me when @twinaphex committed upstream a glew replacement fix (that i first i thought was doing nothing because i was trying to use cmake instead of make to build).
Version/Commit
ppsspp master: dce7dde5e
RetroArch master: 80e45248784d7d47f054487c88875d52df157d11
Environment information
running on wayland with Retroarch build just for wayland/kms and without xwayland/x11 support (to not use xwayland and make the cores and menu slower).