libretro / libretro/RetroArch

Running a game, closing it and opening a new one often crashes retroarch. (Longstanding problem)

Open
#12,389 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

This has been a problem for over a year, now when using SLANGV shaders and VULKAN drivers.
I am very keen to help solve this and will provide whatever information / logs are required to do so.
please just tell me what you need! I've reported this previously and it never gets any comments or feedback,
but there is definitely a problem - something is loading/unloading incorrectly!

Expected behavior

Run a game. Open quick menu, close content, return to main menu. Load a new game, have it run successfully.

Actual behavior

Run a game. Open quick menu, close content, return to main menu. Load a new game, Retroarch attempts to run game, then crashes out. Upon reopening game does not appear in history playlist.

ALSO - In the case of mupen64 after running an N64 game and trying to open another, Retroarch refuses and gives an error message saying loading content failed.

Steps to reproduce the bug
  1. Run a game
  2. Close a game
  3. Open another game
Bisect Results

I think this has been happening since SLANGV shaders and Vulkan were implemented.

Version/Commit

1.9.2

Environment information

Windows 10

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 three-step sequence on Windows 10 with Vulkan drivers and SLANG shaders using RetroArch 1.9.2. Check whether loading a second game after closing the first crashes or reports loading content failed, and whether the game is added to the history playlist. Logs or a bisect are not included, so further investigation is needed to locate the failing component.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
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.