Crash on Exit / Unable to find out why

RetroArch Sony consoles
#1

Hey All,

Coming back to RetroAcrh after a long time, with the mentality “it ain’t gonna beat me this time” I have most up and running, but I came to the PlayStation.

So, I follow the wiki, check the MD5, get it up and running with R3 and L3 to exit… play a game, want to quit back to RetroArch and it crashes with a classic Windows error ‘retroarch.exe has stopped working’ obviously when I hit ‘close program’ it just closes and I have to run it again. (I plan on using RetroArch/ICE/SteamLink, so I really don’t need these type of errors)

Just wondering what I need to activate to see what is causing it (a log file somewhere) or anybody else had similar issues and have a workaround/fix?

I’m running it in a windowed mode, on Windows 10, and the core i"m using is ‘mednafen_psx_hw_libretro.dll’ I’m unable to find the ‘core options’ based of the wiki to change, etc

Anybody help?

#2

core options are just ‘options’ in the quick menu.

if it’s segfaulting on exit, you can try following the instructions in my signature. otherwise, you’ll need to get a backtrace from running with gdb attached. I can walk you through those steps, if necessary.

#3

Appreciate the speedy comeback, so I’ve done the log, it’s visible at

http://pastebin.com/UN6AiHUm

but for the TL;DR; the last bit of it says.

RetroArch [INFO] :: arg #2: -c RetroArch [INFO] :: arg #3: Z:\EmulationSteamLibrary\Emulator\RetroArch\retroarch.cfg RetroArch [INFO] :: arg #4: -L RetroArch [INFO] :: arg #5: Z:\EmulationSteamLibrary\Emulator\RetroArch\cores\mednafen_psx_hw_libretro.dll RetroArch [INFO] :: Resetting undo buffers. RetroArch [INFO] :: Does not have enough samples for monitor refresh rate estimation. Requires to run for at least 4096 frames.

Hope this helps you, help me. :wink:

#4

That log looks okay, actually. The ‘not enough samples’ thing is normal, nothing to worry about. If you’d like to try getting a backtrace, you can download a Windows build of gdb from here: http://www.equation.com/servlet/equation.cmd?fa=gdb drop it into your RetroArch folder, open a command window and type gdb retroarch-debug.exe and then at the gdb prompt, type run --menu --verbose. Then, make it crash (it will just freeze rather than actually going down) and go back to the prompt and type ‘bt’ (for ‘backtrace’).

#5

Hmmmmmmm.

So, I run the 32 bit version, it crashes, with the ‘gdb.exe has stopped working’ (oh, and I also tried the weekly snapshots too, just in case)

gdb.exe retroarch-debug.exe

This binary was built by Equation Solution <http://www.Equation.com>. GNU gdb (GDB) 7.12 Copyright © 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type “show copying” and “show warranty” for details. This GDB was configured as “i686-pc-mingw32”. Type “show configuration” for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type “help”. Type “apropos word” to search for commands related to “word”… retroarch-debug.exe: No such file or directory. (gdb) run --menu --verbose Starting program: --menu --verbose

I run the 64 bit version and I get the following output.

gdb_64.exe retroarch-debug.exe (I renamed it, so I could have both versions in the folder)

This binary was built by Equation Solution <http://www.Equation.com>. GNU gdb (GDB) 7.12 Copyright © 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type “show copying” and “show warranty” for details. This GDB was configured as “x86_64-w64-mingw32”. Type “show configuration” for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type “help”. Type “apropos word” to search for commands related to “word”… retroarch-debug.exe: No such file or directory. (gdb) run --menu --verbose Starting program: --menu --verbose No executable specified, use `target exec’. (gdb)

Any other suggestions/ideas? (although I’ll have to pick this up tomorrow now, as it’s that time of night)

#6

Looks like you’re invoking retroarch-debug.exe rather than retroarch_debug.exe; it’s an easy typo to make.

#7

Ahhhhh, doh, yeah, I just copied and pasted your original text…

I’ve just remoted in to my machine at home and tested it the correct way, and while I’m not able to fully test, the correct command did work.

When I get home from work, I’ll try it with the game, attempt the crash and the report the results. :wink:

#8

Well, I did the BT thingy and I’ve put the results @ pastebin…

I have to say a lot of the results are very ‘whoooosh’ over my head… :slight_smile:

http://pastebin.com/DwyPPCEh

#9

Hmm, that’s a weird error but thanks for getting it. We’ll see what can be done about it.