libretro / libretro/RetroArch

Extreme Slowdown After Suspending to RetroArch Menu

Open
#15,558 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Leaving a game open while in the RetroArch menu will cause loss of audio and an extreme slowdown of gameplay after an unclear period of time. This is not core specific. It is a global behavior it seems.

Expected behavior

Resuming gameplay should result in correct speed and audio, regardless of how long the game is suspended.

Actual behavior

If a game is started and then suspended to the RetroArch menu. The game will resume to extreme slowdown and no audio after a period of time.

An interesting note is this does not affect fast forward speeds. Only normal framerate seems to be affected.

Steps to reproduce the bug
  1. Open any game with any core and reach a point where gameplay speed and audio are apparent.
  2. Suspend to the RetroArch menu for several hours(4-5 at least).
  3. Resume the game and observe that normal speed and audio do not resume.
Bisect Results

To my knowledge, this has been present as long as I have used RetroArch, but I first noticed it with version 1.12.0. I am not certain it occurs on any core, but can 100% confirm it happens with FCEUmm and Beetle PSX HW cores. I think it happens with SNES9x Current as well.

Version/Commit

1581ece

  • RetroArch: 1.15.0(I can also confirm this behavior was present on 1.12.0, so it may be longstanding.)
Environment information
  • OS: Windows 10
  • Compiler: N/A

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

Start by reproducing the issue on Windows 10 with RetroArch 1.15.0, using the FCEUmm or Beetle PSX HW core, and leave the game suspended in the menu for 4–5 hours. Investigate the global resume behavior rather than a core-specific bug; done means normal gameplay speed and audio return after resuming, including at normal framerate.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.