Closed Gagert closed 5 years ago
This is an upstream issue with dosbox, I'm getting the same issue with dosbox standalone on manjaro (read arch linux). When I interrupt the frozen state and back trace from gdb: bt
from /usr/lib/libpthread.so.0
Which indicates that for some reason dosbox is hanging on SDL_Quit(), why SDL1.2 when it's deprecated? Chances of a fix for SDL1.2 nil, probability bug is in dosbox 100%
Correction, I had jackd running for audio, turn off jack, and everything works as expected. Gagert do you use jack audio, if so then I'd recommend disabling it for ALSA fallback.
I just tried the DosBox SVN build, and the exit command no longer crashes DosBox but returns to the RetroArch interface itself (as it should).
Before using the dosbox libretro core, I used either the official DosBox client or an enhanced DosBox build. When setting up a launcher for DosBox, I found good use of inserting an exit command in the selected game's dosbox-config (autoexec), so that both the game and DosBox itself were closed down while quitting the actual game.
As of today, I can't replicate the same function as with the non-libretro DosBox builds. While either auto exiting a game in dosbox libretro, or typing in the actual exit command as the game closes down, nothing happens with dosbox libretro. The core itself freezes, and I have to press F1 to access the RetroArch interface and exit the app that way.
I could just configure an exit key like on the other systems I'm emulating in RetroArch (the escape-key), but as dos-games are designed to be closed down with a "go back to dos" function, it feels more authentic going that way (Quit/Exit button in the in-game menu).