libretro / libretro/RetroArch

Apple: crashes on closing vulkan hw cores

Open
#18,992 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

platform: ios platform: osx
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

In the last few weeks a bug was introduced that causes cores that use a vulkan renderer to crash on content close. I have reproduced this with azahar, beetle_psx_hw, dolphin, flycast, mupen64plus-next with parallel-rdp/rsp, and ppsspp. This happens most easily on iOS but I have also seen it on macOS; I haven't confirmed whether it also happens on tvOS.

Expected behavior

No response

Steps to reproduce the bug
Version/Commit

ff65ab1879

Bisect Results

Bisect has been difficult because of the inconsistency and because of the instability of the branch over the last few weeks.

Present in the nightly version

Yes, this is reproduced in the nightly build

Platform & operating system

iOS 26.4, macOS 26.4

Affected Cores

No response

Environment information

No response

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

No source files, tests, or entry points are identified. First reproduce the crash on iOS or macOS when closing content using one of the listed Vulkan-rendering cores, then compare behavior with the nightly build and commit ff65ab1879. Done means content closes without crashing across the affected cores.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-graphics, desktop-dev, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.