libretro / libretro/RetroArch

[ WiiU ] Recording/Twitch Streaming In RetroArch Causes a Bad Memory Crash

Open
#14,228 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug: recording platform: wiiu
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

I am on WiiU and when I start a recording or start streaming, RA crashes.

Expected behavior

RetroArch shouldn't crash. My gameplay should continue and be recorded or should be streamed depending on which option I picked.

Actual behavior

I get a crash screen when I start recording and I get the same crash when I start to stream to Twitch.

Steps to reproduce the bug
  1. Load RA on WiiU
  2. Enable Recording Menu and set a directory to save recordings to.
  3. Enter Twitch Stream Key into recording/stream settings.
  4. Launch mGBA.
  5. Load any .gb rom.
  6. In quick menu, click start recording or click start streaming.
  7. RA crashes.
Bisect Results

This only started happening once I tried to record or stream from RA. Under recording driver in retroarch.cfg it = "" and I don't have the option to select another driver though the RA menu.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.10.3
Environment information
  • OS: WiiU
  • Compiler: GCC (6.3.0) 32-bit

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 crash on WiiU with RetroArch 1.10.3, using the recording and Twitch streaming options described and the mGBA core with a .gb ROM. Trace the WiiU recording/streaming path from the quick menu and inspect the resulting crash or memory diagnostics; done means gameplay continues while recording or streaming without the bad-memory crash.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.