libretro / libretro/RetroArch

RetroArch aborts with "stack smashing detected" when more than 8 controllers are connected on ARM device

Open
#18,550 12 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

Is there an existing issue for this?
  • This is a bug in RetroArch frontend
  • I have searched the existing issues
Description
$ retroarch
*** stack smashing detected ***: terminated
Aborted
Expected behavior
$ retroarch
# no crash
Steps to reproduce the bug

Connect more than 8 controllers to the system.

Hint: No need to connect real controllers physically; software-only controllers may be created using https://github.com/GrantEdwards/uinput-joystick-demo/

Version/Commit

1.16.0

Bisect Results

No response

Present in the nightly version

I don't know

Platform & operating system

Linux aarch64, Linux armv7l

Affected Cores

No response

Environment information
  • Hardware: Raspberry Pi 3 Model B Rev 1.2
  • OS: Batocera 42 on aarch64, Batocera 39 on armv7l

The error does not occur on x86_64 platform. The error does not occur when <= 8 controllers are connected.

retroarch.broken.log
retroarch.ok.log
retroarch.strace-broken.log
retroarch.strace-ok.log

Relevant log output

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 the listed ARM platforms with more than 8 software-created controllers, then compare retroarch.broken.log, retroarch.ok.log, and the corresponding strace files attached to the issue. Trace the controller-count handling to identify the failing source area; done means RetroArch launches without aborting when more than 8 controllers are connected.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
frontend, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.