You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am reporting a bug in the Onion OS - Any issues with the closed source frontend (MainUI), or RetroArch or any of the cores should be directed to their respective repositories
I have reviewed the Onion Docs and did not find the answer
I have searched the existing (open and closed) issues to ensure I do not log a duplicate
Onions OS Version
4.3.0.1
Miyoo Firmware Version
202407211632
Provide a clear and concise description of the issue
If level 0 logging (debug) is enable in the retroarch settings and saved to the global retroarch configuration, it will cause a crash when trying to save any override file. There is graphical glitching and the following message appears: "The program exited unexpectedly Error code: 139". This does not appear dependent on the specific override file or options you save.
Steps to Reproduce
Enable level 0 (debug) logging for core and frontend in reteoarch settings
Save global retroarch configuration
Restart retroarch and load and override file
Try to save the override file and observe the crash
Provide any additional context or information that may help us investigate your issue
I have isolated the cause to the logging option and have reproduced the issue multiple times with different files.
The text was updated successfully, but these errors were encountered:
Checklist
Onions OS Version
4.3.0.1
Miyoo Firmware Version
202407211632
Provide a clear and concise description of the issue
If level 0 logging (debug) is enable in the retroarch settings and saved to the global retroarch configuration, it will cause a crash when trying to save any override file. There is graphical glitching and the following message appears: "The program exited unexpectedly Error code: 139". This does not appear dependent on the specific override file or options you save.
Steps to Reproduce
Provide any additional context or information that may help us investigate your issue
I have isolated the cause to the logging option and have reproduced the issue multiple times with different files.
The text was updated successfully, but these errors were encountered: