LibNX - Large ROM loading failure

[SeongGino]

Issue:

MAME 2003 (and MAME 2003 Plus) has issues when loading larger ROMsets sequentially in a single user session (I.E. when loading multiple ROMs without exiting to the system menu). These ROMs are otherwise noted to work as intended when loaded separately across different user sessions.

Steps to reproduce:

1. Launch a large-size ROM using a MAME 2003-compatible ROMset: examples include mk2.zip, mk3.zip, narc.zip, etc.
2. Either launch another ROM directly thereafter, or close content and launch another ROM from the same ROMset with the same core.

This will end in a system-level crash (Error 2168-0002, a generic LibNX error)

Steps to reproduce 2:

1. Launch a large-size ROM using a MAME 2003-compatible ROMset: examples include mk2.zip, mk3.zip, narc.zip, etc.
2. Close content and exit RetroArch, returning to the Homebrew Launcher.
3. Load RetroArch again, and load the same or likewise large ROM using a similar ROMset with the same core.

This will end in a RetroArch generic "Failed to load content" error. This will now occur with every subsequent ROM loaded with MAME.

Tested on:

RetroArch: 1.7.5 (LibNX version)

Notes:

A workaround exists, by loading the same/like-sized ROMs but switching between either MAME 2003 or MAME 2003 Plus, depending on the core used directly beforehand, to return to expected behavior. The steps to reproduce above, however, are the same.

This only applies to the LibNX version of RetroArch for Nintendo Switch, and is not a core issue acknowledged on other platforms (I.E. x86_64, ARM, etc.). This has been tested using Homebrew Launcher as a system application, meaning RetroArch has a total ~400MB available RAM to use. This issue has been noted since before the official RetroArch for Nintendo Switch release (formerly known as "RetroNX").

[mahoneyt944]

@SeongGino is this still an issue with our current build?