Mac OS ARM M1 Pro constantly crashes

[personaone]

First and foremost consider this:

• This is a DEVELOPER oriented channel dedicated to report bugs and suggest features about the libretro core, please do not ask for help. If you need help, go to https://forums.libretro.com/;
• The upstream bug tracker is a forum thread, located at https://forum.fobby.net/index.php?t=msg&th=1114;
  • Note: As of October 2018, Microsoft email providers (think email addresses ending with hotmail/live/outlook) are rejecting email from the forum. If you want to register an account in the upstream project's forum, consider using another mail provider.
• For game-related bugs: 1) First, check if it's already reported on the upstream bug tracker; 2) If it's not reported there, try to reproduce the bug with mednafen; 3) If it's reproducible with mednafen, report it on the upstream bugtracker; 4) If it's not reproducible with mednafen, ONLY THEN should you report it here. 5) DO NOT report Beetle-specific bugs on the upstream tracker.

Description

Retroarch crashes on loading a game, sometimes it load successfully, sometimes it crashes. This is very inconsistent, other cores like SNES/Sega don't behave this way. Sometimes a restart fixes this, sometimes it doesn't - very random. I'm attaching a crash log.

Expected behavior

Expectation is that the game just runs, like any other core [Photos/videos of original hardware behavior and/or mednafen behavior]

Actual behavior

Frequently when loading games, Retroarch crashes [Photos/videos of the core's behavior]

Steps to reproduce the bug

1. Load the PSX-Beetle core
2. Load a game
3. [and so on...]

Bisect results

Hard to tell, it's very random

Version/Commit

[If you're using RetroArch, this information is on the bottom left after loading the core. You can do this via Main Menu -> Load Core]

• Beetle PSX: 0.9.44.1 bd6b9ef (latest from auto updater)

Please specify whether you are using Beetle PSX or Beetle PSX HW.

Core options

Mem card type: Mednafen, Show full overscan, Custom Aspect ratio 8x

Please also specify, if reporting a graphical glitch for Beetle PSX HW, your "Renderer" core option setting and your frontend selected video driver.

Environment information

• Frontend: Retroarch 1.11.1
• OS: Mac OS 12.6
• Compiler: N/A stable release
• GPU: N/A software mode

psx.txt

[hizzlekizzle]

Can you generate a log in RetroArch that captures a crash?

there are a few ways to get a log, but the easiest is to go to settings > log and set both logging verbosities to DEBUG and 'log to file' to ON. Do whatever it takes to reproduce the offending behavior and then close RetroArch (if needed). It will then create a log file in your 'log' directory, which you can open in a text editor. If you want us to take a look at it, copy/paste the log contents somewhere like pastebin.com and then post a link to it here (this is more convenient for people than having to download it and open it in our own text editors)

[personaone]

Can you generate a log in RetroArch that captures a crash?

there are a few ways to get a log, but the easiest is to go to settings > log and set both logging verbosities to DEBUG and 'log to file' to ON. Do whatever it takes to reproduce the offending behavior and then close RetroArch (if needed). It will then create a log file in your 'log' directory, which you can open in a text editor. If you want us to take a look at it, copy/paste the log contents somewhere like pastebin.com and then post a link to it here (this is more convenient for people than having to download it and open it in our own text editors)

Sure

https://pastebin.com/V6rpxFXF

crashes straight to desktop on loading content. Not always - so it's really inconsistent too.

[personaone]

I think I'm starting to notice a trend here, for some reason whenever I pull a new core by using the Update Installed Cores option, the newly installed core crashes when loading content. This is actually affecting this core, where the example the Genesis Plus GX one just runs no problem straight after updating. The PSX core runs only after a few reboots - so it might have something to do with maybe file permissions that don't get updated after a new core is updated? Here's another log file with logging to both core and RA. I don't see any errors though....

https://pastebin.com/Bk4xCHjG