[WiiU] Possible Freeze if Fast Forward Rate is set above 2.0x
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
(I would put this down to a Core issue but seeing as it happens on multiple Cores I thought I'd put it in as a Retroarch issue)
Description
It's possible for some Cores to freeze when Fast Forward bind is held if the Fast Forward Rate is set above 2.0x the default is 0.0x - unlimited (no FPS cap) although the Core has crashed every now and again you can hear a note of the games music play suggesting the Core hasn't froze but more slowed down to a crawl??
Expected behavior
Expected to be able to use Fast Forward Rate at 0.0x (no FPS cap) without the Core freezing.
Actual behavior
If the Fast Forward Bind is held while the Fast Forward Rate is set above 2.0x there's a possibility of a Core freeze
Steps to reproduce the bug
- Load one of the GB,GBA,MS Cores with default Fast Forward Rate set
- Get ingame
- Hold the Fast Forward Bind (happens pretty randomly, but should happen after a few press/holds of the FF Bind Button)
Bisect Results
This is a long standing issue, matter of fact it always ? happened as far as I can tell
- OS: WiiU
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 freeze on WiiU with the GB, GBA, or MS cores, using the default Fast Forward Rate and holding the Fast Forward bind repeatedly. Compare behavior at rates above 2.0x and at 0.0x; done means fast forward no longer freezes or slows the core to a crawl.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100