-
Notifications
You must be signed in to change notification settings - Fork 116
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
[Regression] AttractMode Lockup (FeFileInputStream) #440
Comments
- I am unable to recreate issue #440 but I noticed that the frontend is attempting to load image files set from layout scripts without first checking if the file exists. I have added code to check if the file exists before trying to run it, perhaps this will fix the issue.
HI, thanks for the report. I am unable to recreate this lockup myself but I have found a potential cause that I have now fixed in the code. I would appreciate it if you could try the latest code in the master banch and let me know if it might address this issue. cheers |
Fantastic. That seems to work, thanks @mickelson I have a feeling this is triggered by a new(er) version of SMFL and Arch is likely ahead of the versioning curve there so we got hit first. What an odd change. |
Found a secondary issue to this; whilst this fixed file browsing, the issue still seems to trigger when the screensaver runs so it looks like you need to add the file-exists checks there too. |
I'm not sure what's triggered this to be an issue, but recently I noticed AttractMode would lock up if I browsed to a game that didn't have a complete set of artwork.
I bisected the issue back to this commit - 826ff62
Now that commit isn't recent and I've definitely been using AttractMode since then, so I'm wondering if some system library change has caused this (file streaming) to suddenly fail.
The problem manifests itself like so: If you browse to a game that doesn't have all the artwork that the theme looks for, AttractMode just seems to lock up indefinitely. No errors, it just freezes.
Here's a backtrace after waiting a few minutes after the freeze (I triggered the interupt):
The text was updated successfully, but these errors were encountered: