Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RetroArch crashes with hardware-based cores #17393

Open
2 tasks done
toao1985 opened this issue Jan 11, 2025 · 0 comments
Open
2 tasks done

RetroArch crashes with hardware-based cores #17393

toao1985 opened this issue Jan 11, 2025 · 0 comments

Comments

@toao1985
Copy link

Is there an existing issue for this?

  • This is a bug in RetroArch frontend
  • I have searched the existing issues

Description

General System Information: x86_64 machines, running Ubuntu-based distributions as the operational system. AppImage release of RetroArch v1.20.0. Video driver selected as vulkan. Cores fully updated by the date of this report.


Some specific actions make RetroArch crash, which materializes as the application suddenly and promptly closing, as if it was forcibly closed through a task manager. That behavior tends to happen with many hardware-based cores, listed below.

Expected behavior

No response

Steps to reproduce the bug

Small exception

  • Mupen64Plus-Next core crashes
    • Happens when you load a game and select "restart" in RetroArch's quick menu.
    • But only when using ParaLLEl.
    • Works fine with GLideN64.
    • It actually freezes, not crashes. Need to be manually terminated through a task manager.
    • Doesn't generate a useful log file.

Version/Commit

1.20.0 (Linux AppImage Release)

Bisect Results

No

Check in the nightly version

I don't know

Platform & operating system

Linux 64-bits, Ubuntu-based distributions

Affected Cores

Flycast, PPSSPP, Dolphin (all latest versions).

Environment information

  • Window manager: x11
  • Video driver: vulkan
  • Installed through AppImage

Relevant log output

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant