@BuZz Thanks a lot. In the end i went for flycast since all posts went that direction.

If I connect the dots here and in addition to the merged changes [1] @pjft was referring to, I see also the option that the file log might choke caused by a specific combination of many log writes, threaded loading and slower file operations by rpi3 and/or sd-card (or even undervoltaging, which is crucial to sd-card operations).

While I am unable to reproduce it, it might be considered to reduce the log output of missing theme resources by lowering the log level (WARNING to DEBUG). It would reduce the probability of file log chokes and would also speed up the normal ES boot:

diff --git a/es-core/src/ThemeData.cpp b/es-core/src/ThemeData.cpp index cb1b265..45b54a6 100644 --- a/es-core/src/ThemeData.cpp +++ b/es-core/src/ThemeData.cpp @@ -517,11 +517,11 @@ void ThemeData::parseElement(const pugi::xml_node& root, const std::map<std::str if(!ResourceManager::getInstance()->fileExists(path)) { std::stringstream ss; - ss << " Warning " << error.msg; // "from theme yadda yadda, included file yadda yadda + ss << " Message " << error.msg; // "from theme yadda yadda, included file yadda yadda ss << "could not find file \"" << node.text().get() << "\" "; if(node.text().get() != path) ss << "(which resolved to \"" << path << "\") "; - LOG(LogWarning) << ss.str(); + LOG(LogDebug) << ss.str(); } element.properties[node.name()] = path; break;

Additionally a mutex for log file write operations might be used as outlined here [2] to make fprintf() [3] thread safe.

[1] github.com/RetroPie/EmulationStation/pull/774/files#diff-20f861dd5841312f45eb90d5a56cd5addad0657c66605d6235696a345907e15d
[2] https://stackoverflow.com/questions/43427405/c-writing-to-a-file-in-multithreaded-program
[3] https://github.com/RetroPie/EmulationStation/blob/52c04d77864287aa0ae7f484460966d8253079df/es-core/src/Log.cpp#L77

@mitu
At the risk of you guys either laughing or scoffing at me a bit, the issue I was having is gone. I had the system freeze problem for about a month before I finally called for help on the forum, and it literally stopped happening basically as of yesterday. I will definitely look at the system log should it happen again.

@roslof I'm running into the same problem that you had originally with emulation station hanging and freezing. I'm trying to find the .cpp file that you noted so I can amend the vlc options to "original" but am having no luck. Can you point me to the directory where I would find the file or the command line prompt to load it

@barbudreadmon said in Asura Buster Game freezing?:

@arcadez2003 Thanks for pointing out it was an issue with m68k intf, i had looked into the game driver and couldn't find the fix.
I did a PR at https://github.com/libretro/fbalpha2012/pull/99, but i believe such change will have a performance cost, even on classic m68k games (additional condition on every cycle, and the code for 68ec020 looks like it'll be slower).

The emu gods giveth and they taketh away :)

@lostless I set the system to save from RAM every second and the issue appears to be fixed not just corrected. I was also getting little periods were the sound was muted and that also seems to have stopped. I was assuming that was a different problem and that was why I did not include that in the original question, but that has stopped as well. Great information thank you.

@h4ckerv2 I tested some things at the same time but I thing all the things together solved the issue:
-Change the psx bios to another of another website
-Disable the screensaver in all places (rpi and retropie), in rpi you will need to install first a screensaver and disable it after.

Maybe this helps someone.
I had a similar issues on Rearmed core on RetroArch on the switch.
The game would sometimes get stuck in a state if you pressed pause or inventory the game would freeze.
It happened to me in certain sections of the game

on a water level with crumble blocks above spikes after a slide (I somehow wondered back and did more things and I fixed it). on the last room of the barkhang monestary after putting in the prayer wheels. It forces you to put in an item and open up the inventory and freezes

I did manage to save the game before this in the pause menu book (you have to do it before getting into that state where pause crashes the game). Copy the save file .srm, play it on PC (same emulator but x86) finish the level, save and reload onto switch (or your retropie).

Sadly if you rebind quicksave and quickload not to pause the game as a workaround it will eventually force you to open the inventory and freeze the game.

Not ideal but possible not to loose all progress and potentially keep playing on

Hi, this also happens to me. No problems with Pi 3B+, but I just got a new Pi Zero W, and freezes all the time with RetroPie.

I've tried this versions:

Retropie 4.5.1 -> when it freezes I stil can do F5 in Web Manager and see the temperature, or sometines reboot with Putty if I already had one session opened. And one of those times, Putty threw this when it froze:

pi@retropie:~ $ Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.163849] Internal error: Oops: 837 [#1] ARM Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167201] Process emulationstatio (pid: 681, stack limit = 0xcebb6188) Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167355] Stack: (0xcebb7fa8 to 0xcebb8000) Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167463] 7fa0: be82d520 00000001 be82d520 00000001 00000000 00000003 Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167653] 7fc0: be82d520 00000001 00000004 000000a8 00000000 00000000 00000005 00000000 Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167844] 7fe0: 00000000 be82d518 00000000 b66ea124 80000010 be82d520 00000000 00000000 Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.168038] Code: f10c0080 e5992008 e35204bf 1b000de1 (e5991000)

RetroPie 4.5 -> Also freezes randomly.

RetroPie 4.4 -> Also freezes, but exits EmulationStation and shows "Segmentation Fault". I have and screenshot if you need it.
And Putty threw this:

pi@retropie:~ $ Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.770533] Internal error: Oops: 805 [#1] ARM Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773455] Process emulationstatio (pid: 444, stack limit = 0xc0e68188) Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773619] Stack: (0xc0e69e48 to 0xc0e6a000) Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773741] 9e40: 00000010 00000000 00000020 00000030 00000030 00000020 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773942] 9e60: 00000200 c0e69e8c c0e69edc c0e69e78 bf078ba0 c015a1e4 cd592b60 c0e69ea0 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774148] 9e80: c1eaec00 0000b00a 00000001 be9481d8 c0e69ea8 00000000 00000000 00000ff0 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774353] 9ea0: 020a4371 00000ff0 c13b8de0 cd5dc660 c0e69eec c0e69ec0 c004c3a0 c0623aec Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774556] 9ec0: c004c99c c0040a14 00000000 c13b8de0 00000001 cea06f00 c0e69f1c c0e69ee8 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774755] 9ee0: c0046b2c be9481b4 cf2edd88 c9627320 00000004 00000004 c0e68000 00000000 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774956] 9f00: c0e69f7c c0e69f10 c016c824 c05025c4 c0e69f74 c0e69f20 c063068c c0046adc Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775156] 9f20: c0e69f44 c006fae0 c0e69f6c c0e69f38 3cbc4f68 c01773f8 cb6ef900 b5feb564 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775358] 9f40: be9481b4 be9481d8 400cc404 00000004 c0e69f6c c9627321 be9481b4 c9627320 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775562] 9f60: 400cc404 00000004 c0e68000 00000000 c0e69fa4 c0e69f80 c016cf20 c016c794 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775762] 9f80: 0000b00a b5feb564 be9481b4 be9481d8 00000036 c000ffa4 00000000 c0e69fa8 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775963] 9fa0: c000fe00 c016cee8 b5feb564 be9481b4 00000004 400cc404 be9481b4 0000b00a Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.776164] 9fc0: b5feb564 be9481b4 be9481d8 00000036 00000000 be948374 003be5cc 02164608 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.776365] 9fe0: b5feb240 be9481a4 b5fd8c08 b66ef80c 80000010 00000004 00000000 00000000 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.777184] Code: e51f1528 e24b207c ebffea8d e1a09000 (eafffc25)

RetroPie 4.3 -> Also freezes

NOOBS_v2_8_2 -> Raspbian Ok, update everything..., until I install RetroPie manually, then it freezes right away!

I have to try Recalbox...

@fastpop72 for what it's worth, i opened an issue about it last year : https://github.com/libretro/reicast-emulator/issues/232 , i think yours is related.