Closed kivutar closed 2 years ago
This happens to me when I try to Save State on NES or Gameboy the OSD comes up and says retro_serialize failed.
This seems to happen when I play snes and sega then switch over to nes and savestate I get the retro_serialize failed. If I reboot and just play nes its fine
I'm still getting this error even with the latest version of ludo on both my Pi3 and Pi4. Any idea what may be causing this? I was thinking maybe a memory leak i'm just not sure
No idea for now
Okay I have more info
Hardware Tested: Raspberry pi 3b+ and Pi4 on LudOS Latest version, also on a PC with Ubuntu 20.04 and LUDO 0.12.0 with Gameboy, NES, SNES and Sega
Steps to Reproduce
I was able to reproduce the issue all the time.
Now heres the weird thing
It seems if you load up any nes game upon boot then play any other system and go back to nes and save state it works
This is weird and dont understand it, but maybe this will give a clue on whats going on.
Also it appears Game Boy is Affected as well load up any nes, snes sega then load up a gameboy game and choose to save you will get a retro_serialize failed.
Another Interesting bit, If you load up gameboy game then load up an NES game then try to save it also give Retro_Serialize failed.
The Bug appears to be with the NES and Gameboy Emulator
This should be fixed with my last change.
Reopen if it's still happening
Hi @kivutar I have noticed this is still happening. Seems to happen with the Gameboy Emulator and NES Emulator
The easiest way to replicate on initial boot:
You will get the retro_serialization failed and no save will be saved
This must be done on initial boot
however if you run
NES core first the problem doesnt happen you can switch to another core and then back to NES and save states will work
Its a really odd issue
Same here, it doesn't happen on OSX for me. Something is wrong, but the steps to reproduce won't always work.
This is fixed! =] Thanks @kivutar Im not sure what commit fixed it but its working like a charm
I think commit 6c2a6cf89ade4bc87a303d526653c3a4cb88322b fixed the issue
OK cool :D
Happened a few times on RPi with fceumm: