-
Notifications
You must be signed in to change notification settings - Fork 44
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
Crash on selecting 'Images' #203
Comments
This seems to be a problem with one of the thumbnails for the images being corrupt or something. I will try to fix it by just letting boilr ignore it if it can't parse the image. |
This should be solved in version https://github.com/PhilipK/BoilR/releases/tag/v.1.4.4 now. Let me know if it does not work for you. |
@PhilipK This issue is not resolved for me in 1.4.4. I get same symptoms, crashing when I select 'Image', the terminal output is thus:
|
I am going to reopen this, it turns out to be a bug in the library that decodes the images, if the images are webp format. I will see if I can make a pull request for the image library or maybe just ignore all webp images or something in boilr. |
@ak-42 can you (or anyone that experiences this bug) try to run this beta version? https://github.com/PhilipK/BoilR/releases/tag/v.1.4.4-beta |
@PhilipK I'm having trouble installing the file directly. The documentation says it should be just |
Oh, that is not a flatpak release. |
Oh, sorry, didn't even occur to me that it'd be a binary on its own. Well, it still crashes. Here's the terminal output:
The last two lines only occur when the 'Images' is clicked, rest upon launch. |
I simply can not figure out that kind of input (image) that would cause this. @ak-42 Would it be possible for you to zip your steam grid folder (the one containing all your custom images) and upload it? It could just be the webp images, as it seem from the log that it is an .webp image that is causing the crash. |
@PhilipK You can download all the .webp files from https://send.vis.ee/download/0d90a4c137b45ede/#WZoQWJ9npqGy4rXLgJ81SA Please note that this link will expire after 1 successful download or within 7 days, whichever comes first. I cannot open |
That helps a lot! I will look at doing some validation later today (after work) |
I got the files, you can delete all those webp images, that should get you around the crash. |
I found the cause of the problem, they are animated webp images, the image library used panics when it tries to load them. |
Alright, https://github.com/PhilipK/BoilR/releases/tag/v.1.4.4-beta2 can you try the newest beta. |
@PhilipK If this is for me, I can no longer replicate the crash as I've deleted the webps and the crash no longer occurs even on the current stable unfixed version. |
This should be fixed in the newest version, if it comes up again, I will reopen this issue. |
Still crash on newest version (both the flatpack or linux executable) on steam deck when choosing "images" tab
|
Sorry to be that guy, but: If you have the native version, could you try to run RUST_BACKTRACE=1, so I can see the stacktrace? |
Hi , no worries, I am running the native 1.4.7 (only got my deck 2 days ago) here are the output
|
Again, this is some kind of panic in the image-rs package, and again it is related to webp. |
Hi, could you tell me where would I find the folder? I have narrowed down to which game causes the crach, it is the Tunic |
Nvm, i have narrowed down to these two webp. |
Thanks, I can reproduce the error with those images |
This is solved in the newest version: Thanks for helping out |
I am running BoilR on Steam Deck, with latest system software and up to date BoilR from Flathub.
The program starts fine, but when 'Images' is selected on the left side of the main Window, it crashes. Here's the output from the terminal:
I've tried to run Rust backtrace as suggested in the error, by running
flatpak run io.github.philipk.boilr --env='RUST_BACKTRACE=1'
but it does not seem to work. I am uncertain if I'm not doing something right, or the error message is wrong/outdated.Please let me know if there's anything further I can do to provide diagnostic info.
The text was updated successfully, but these errors were encountered: