-
-
Notifications
You must be signed in to change notification settings - Fork 216
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
Caesium silently crashes when compressing corrupted files #303
Labels
Comments
The link you provided for the image seems unreachable on my side. Can you please provide an alternative link or way to download the image? |
Seems an issue with resizing, as the program crashes trying to downsize the image. As a temporary solution while I try to fix it, you can try disabling resizing, compressing with Caesium, and then resizing the image with Caesium again (or another software). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
While compressing corrupted files, Caesium silently crashes due to the file being corrupted.
The specific file in question is this: https://readcomicsonline.ru/uploads/manga/firefly-malcolm-reynolds-year-one-2024/chapters/1/34.jpg
Software version
2.7.1
Operating System information
Windows 11
To Reproduce
Steps to reproduce the behavior:
If there's a long list of files to be processed, some of them will be compressed, some not.
Expected behavior
Caesium shoud handle the corrupted file gracefully, ignoring its processing, but completing the other files on the list. A warning message in the 'Information' column, informing about the corrupted file not being processed would be great.
Application Log
I tried to get the log, but, as the program crashes, no information about the corrupt file is registered.
Additional context
When opening the file in Adobe Photoshop, it says the file is truncated or incomplete and then asks if I want to open it anyway. If I click Yes, the file is opened, but the bottom part is blank.
I searched for similar issues, and found #200 and #239, both are closed.
Here's my usage data:
The text was updated successfully, but these errors were encountered: