Open ms2048 opened 3 years ago
Hopefully my fresh finding works on Switch too.
Sorry, it still crashes on f792847, with exactly the same steps to reproduce...
Just in case, I am uploading logs (steps taken like in a description), maybe these will help
retroarch2021_01_0701_11_36.log retroarch2021_01_0701_12_18.log retroarch2021_01_0701_13_07.log
Sorry, nothing useful in those logs for my eyes..
Is there a debug version of RA for Switch which does a crash dump?
I don't think so. Debugging under Switch seems very limited overall.
Also, correct me if I'm wrong, but the whole 'Salamander' thing (https://docs.libretro.com/development/retroarch/glossary/) means that the special debug version of the core itself would be needed for it to behave differently.
Any difference with the latest changes?
Both stable (official) RA 1.9.1 version and the updated 86ed900 one still crash after reloading
still no luck with cf9ba7c
I'm on RetroArch 1.9.0 on Nintendo Switch with newest core available from Core Updater (PUAE 2.6.1 e187a61). Additionally, I have observed the same behavior in an older build (bundled within RetroArch 1.9.0 for Switch).
To trigger a crash it is enough to just 'Load Core -> Commodore Amiga (P-UAE)', 'Start Core', (wait a few seconds and then enter a RetroArch menu), 'Close Content', 'Load Core -> Commodore Amiga (P-UAE)' (which is NOT the same as 'Start Core') and then it crashes with 'The software was closed because an error occured'. Tried with different cores, games, even quitting and re-launching RetroArch or different homebrew. Tried with fresh config for P-UAE, all sysmodules disabled, etc. and still no deal.
So this looks like some memory leak inside P-UAE.