libretro / libretro/RetroArch

[Android] RetroArch stop responding during emulation via certain cores

Open
#12,701 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

core bugs - not retroarch bugs
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

So far, I've encountered this weird issue on 2 separate game on 2 different cores:

Legend of Zelda: a link to the past on the bsnes and,
Pokemon fireRed rom with "Pokemon unbound" patch on the mGBA.

Expected behavior

Retroarch should continue to run emulator games normally until the core or Retroarch is closed.

Actual behavior

After playing for a while, Retroarch randomly freeze, and Android displays "retroarch is not responding" message, requiring me to force close the app and lost game progress.

Steps to reproduce the bug
  1. Load the ROM in selected core
  2. Play normally until freeze
Bisect Results

Happens ever since the first time I play the ROM.

Version/Commit

You can find this information under Information/System Information

  • Git version: 5c2f79a
  • RetroArch: 1.9.7_GIT
Environment information
  • OS: Android 11
  • Compiler: -
  • input device: bluetooth controller

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin by reproducing the freeze on Android 11 with the listed RetroArch version, bluetooth controller, bsnes and mGBA cores, and the two reported ROM cases. Since no source file or test is identified, first determine whether the hang is in RetroArch or a core; the issue is done when the cause is isolated and a reproducible fix is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, c
Domain
game-dev, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.