The AI service on japanese games make retroarch crashes with GBA cores
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
after the last retroarch's update, after making about 10 translations with the AI service on a GBA core, retroarch crashes
I have tried also with an old version (1.8.5) but the translation doesn't seem to work anymore, it doesn't behave as in the way of the last version (1.8.8), instead of crashing it stops translating
this concerns, when I could see, only the cores destined for the emulation of the gba
I tried with these games:
legacy of goku 2 (international)
Astro Boy: Omega Factor (Europe)
Expected behavior
Ai translations on gba cores should take place successfully without a software crash, as in older retroarch versions.
Actual behavior
making a translation from a gba core crashes the software (I don't know if it is actually limited to Japanese language games or specific games).
Steps to reproduce the bug
- start a GBA game in japanese with any core for the gba (Beetle GBA, gsSP or mGBA)
- when a Japanese text to be translated appears, press the hotkey for ai translation
- after about ten translation times the software will crash.
Version/Commit
- RetroArch: [1.88]
Environment information
- OS: [Windows 10]
- Compiler: [MinGW (9.2.0) 64-bit] (standard I think)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash on Windows 10 with RetroArch 1.88, a Japanese GBA game, the AI translation hotkey, and the named GBA cores: Beetle GBA, gpSP, and mGBA. Compare behavior across the listed games and cores after repeated translations; the issue is done when translations continue without RetroArch crashing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100