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 v1.20.0 crashing at Wii U menu interaction #17377

Open
2 tasks done
filobeddo opened this issue Jan 9, 2025 · 8 comments
Open
2 tasks done

Retroarch v1.20.0 crashing at Wii U menu interaction #17377

filobeddo opened this issue Jan 9, 2025 · 8 comments

Comments

@filobeddo
Copy link

filobeddo commented Jan 9, 2025

Is there an existing issue for this?

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

Description

I updated my WiiU Retroarch install (from v1.19.1) to v1.20.0. Initially OK when loading a core/content (Snes9x), however after I closed the content and began navigating around the UI a crash/exception occurred.

I reloaded and check a different core/content (Fuse) and found the same; a crash after closing and then brief navigation around the UI.

[ Update: I since found the specific UI navigation to be opening the 'load content' option to explore files ]

As I had upgraded I had kept my original configuration/save files etc. To eliminate some inconsistency with those I went back and did a fresh folder install of Retroarch (for my WiiU SD card) and tried again with no prior/save configurations.

The same result, a crash after existing a core and UI navigation.

Expected behavior

Normal UI navigation (without hard exception/crash)

Steps to reproduce the bug

In WiiU Retroarch:

  1. Load a core/content.
  2. Exit that content.
  3. Navigate around in load content
  4. Exception occurs.

Version/Commit

1.20.0

Bisect Results

No response

Check in the nightly version

I don't know

Platform & operating system

Wii U

Affected Cores

Snes9X (main) and Fuse at least (suspect all cores but have not tested more as yet)

Environment information

Wii U
Screenshot 2025-01-09 184957
Screenshot 2025-01-09 185007

Relevant log output

No response

@LibretroAdmin
Copy link
Contributor

Try seeing if this same issue happens if you enable 'Filter by Current Core'.

To enable this, go to Load Content -> File Manager. Turn on 'Filter by Current Core' there, then exit RetroArch for the changes to take effect.

If the crash does not happen then, then at least I know where the issue occurs.

@Ploggy
Copy link

Ploggy commented Jan 12, 2025

@filobeddo If you still having this issue try deleting your retroarch.cfg and see if that fixes you problem.

@filobeddo
Copy link
Author

Try seeing if this same issue happens if you enable 'Filter by Current Core'.

To enable this, go to Load Content -> File Manager. Turn on 'Filter by Current Core' there, then exit RetroArch for the changes to take effect.

If the crash does not happen then, then at least I know where the issue occurs.

Hi. Well done, you've honed in the fault straight away.

When I apply ' filter by current core ' (exit/restart) the exception/crash no longer happens. I was able to use the app as normal and change cores/content with no issues.

I then turned that feature back to default (exit+restart) and found that the crash would occur as before.

I did turn on logging, however it did not seem to capture the actual crash; so a job for your debugging.

Well done and thanks, workaround now available to use v1.20 on WiiU until this error is fixed.

Simon.
retroarch.log

@filobeddo
Copy link
Author

@filobeddo If you still having this issue try deleting your retroarch.cfg and see if that fixes you problem.

Thanks, i'd already tried this before posting this report.

See the other comments, the root cause of the problem has now been found and a workaround is available:

"go to Load Content -> File Manager. Turn on 'Filter by Current Core' there, then exit RetroArch for the changes to take effect."

@filobeddo
Copy link
Author

Potential cross-reference to #17430 which I just reported.

@LibretroAdmin
Copy link
Contributor

We need a bisecting of this. We already asked one sometime ago if he could bisect. He said he would then he never got back to us.

I have to mention that the longer it takes for someone to bisect this, the harder and harder it will become to actually fix this bug at all.

@filobeddo
Copy link
Author

We need a bisecting of this. We already asked one sometime ago if he could bisect. He said he would then he never got back to us.

I have to mention that the longer it takes for someone to bisect this, the harder and harder it will become to actually fix this bug at all.

I am guessing I cannot assist with the above, but happy to if I had details of exactly what is needed.

@LibretroAdmin
Copy link
Contributor

You will need to find out when this started happening. Through checking nightlies or by going back to prior commits, compiling it and then testing it on the device.

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

3 participants