Closed SuperSonic472 closed 7 months ago
Note: You might need to finish a few stages before the glitch happens.
Could you upload a save file that allows this issue to be easily reproduced?
I don't think it needs a save but here Download
Just attaching some error logs related to this.
2023-08-27 19:49:40.543 30469-30668 libc me.magnum.melonds.dev A melonDS-android/melonDS-android-lib/src/ARMJIT_A64/ARMJIT_Compiler.h:108: Arm64Gen::ARM64Reg ARMJIT::Compiler::MapReg(int): assertion "RegCache.Mapping[reg] != Arm64Gen::INVALID_REG" failed
2023-08-27 19:49:40.544 30469-30668 libc me.magnum.melonds.dev A Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 30668 (Thread-15), pid 30469 (num.melonds.dev)
---------------------------- PROCESS STARTED (31401) for package me.magnum.melonds.dev ----------------------------
2023-08-27 19:49:41.298 31399-31399 DEBUG crash_dump64 A Cmdline: me.magnum.melonds.dev
2023-08-27 19:49:41.298 31399-31399 DEBUG crash_dump64 A pid: 30469, tid: 30668, name: Thread-15 >>> me.magnum.melonds.dev <<<
2023-08-27 19:49:41.299 31399-31399 DEBUG crash_dump64 A #02 pc 000000000042dc50 /data/app/~~AHQsapR29TvkkN_FedGpfw==/me.magnum.melonds.dev-MLwnZze2m2pBuld203dFPg==/lib/arm64/libmelonDS-lib.so (ARMJIT::Compiler::Comp_MemAccess(int, int, ARMJIT::Op2, int, int)+2412) (BuildId: afa38a6d46c0c6927fe2fc88d4495109d8013022)
2023-08-27 19:49:41.299 31399-31399 DEBUG crash_dump64 A #03 pc 000000000042dffc /data/app/~~AHQsapR29TvkkN_FedGpfw==/me.magnum.melonds.dev-MLwnZze2m2pBuld203dFPg==/lib/arm64/libmelonDS-lib.so (ARMJIT::Compiler::T_Comp_LoadPCRel()+116) (BuildId: afa38a6d46c0c6927fe2fc88d4495109d8013022)
2023-08-27 19:49:41.299 31399-31399 DEBUG crash_dump64 A #04 pc 0000000000429360 /data/app/~~AHQsapR29TvkkN_FedGpfw==/me.magnum.melonds.dev-MLwnZze2m2pBuld203dFPg==/lib/arm64/libmelonDS-lib.so (ARMJIT::Compiler::CompileBlock(ARM*, bool, ARMJIT::FetchedInstr*, int, bool)+952) (BuildId: afa38a6d46c0c6927fe2fc88d4495109d8013022)
2023-08-27 19:49:41.299 31399-31399 DEBUG crash_dump64 A #05 pc 000000000040edf8 /data/app/~~AHQsapR29TvkkN_FedGpfw==/me.magnum.melonds.dev-MLwnZze2m2pBuld203dFPg==/lib/arm64/libmelonDS-lib.so (ARMJIT::CompileBlock(ARM*)+4376) (BuildId: afa38a6d46c0c6927fe2fc88d4495109d8013022)
2023-08-27 19:49:41.299 31399-31399 DEBUG crash_dump64 A #06 pc 000000000039c328 /data/app/~~AHQsapR29TvkkN_FedGpfw==/me.magnum.melonds.dev-MLwnZze2m2pBuld203dFPg==/lib/arm64/libmelonDS-lib.so (ARMv5::ExecuteJIT()+480) (BuildId: afa38a6d46c0c6927fe2fc88d4495109d8013022)
2023-08-27 19:49:41.299 31399-31399 DEBUG crash_dump64 A #07 pc 00000000003ea12c /data/app/~~AHQsapR29TvkkN_FedGpfw==/me.magnum.melonds.dev-MLwnZze2m2pBuld203dFPg==/lib/arm64/libmelonDS-lib.so (unsigned int NDS::RunFrame<true, 0>()+532) (BuildId: afa38a6d46c0c6927fe2fc88d4495109d8013022)
2023-08-27 19:49:41.299 31399-31399 DEBUG crash_dump64 A #08 pc 00000000003e9b0c /data/app/~~AHQsapR29TvkkN_FedGpfw==/me.magnum.melonds.dev-MLwnZze2m2pBuld203dFPg==/lib/arm64/libmelonDS-lib.so (NDS::RunFrame()+72) (BuildId: afa38a6d46c0c6927fe2fc88d4495109d8013022)
2023-08-27 19:49:41.299 31399-31399 DEBUG crash_dump64 A #09 pc 0000000000382470 /data/app/~~AHQsapR29TvkkN_FedGpfw==/me.magnum.melonds.dev-MLwnZze2m2pBuld203dFPg==/lib/arm64/libmelonDS-lib.so (MelonDSAndroid::loop()+32) (BuildId: afa38a6d46c0c6927fe2fc88d4495109d8013022)
2023-08-27 19:49:41.299 31399-31399 DEBUG crash_dump64 A #10 pc 0000000000012048 /data/app/~~AHQsapR29TvkkN_FedGpfw==/me.magnum.melonds.dev-MLwnZze2m2pBuld203dFPg==/lib/arm64/libmelonDS-android-frontend.so (emulate(void*)+284) (BuildId: f3c2742dada2dc26e0c9e394bbc276ce6b8f0fc3)
This should be fixed by commit 395be1d. Try the latest nightly release once it's ready and let me know if it's fixed 🙂
My phone does run all games at full FPS.
Problem:
Pretty self explanatory, the game crashes when entering a loading zone like a door or warp star.
Steps to reproduce (I recommend using the decrypted version from r/roms):
Video:
https://github.com/rafaelvcaetano/melonDS-android/assets/64370131/35457a8d-6e73-4333-bffa-a27b6c00c187