-
-
Notifications
You must be signed in to change notification settings - Fork 192
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 crashes during working. #98
Comments
Seems related to #56 (comment) |
Can you try the same process with the option "Keep metadata" unchecked and see if it works? |
I checked it as suggested – same result, i.e. crashes.
Attached the file that causes the problem – unclear if it is file related.
|
I did not receive the attachment unfortunately. I'm testing with various setups, but seems to work consistently. |
Here is a test folder that constantly keeps crashing during compression. All i do is drag and drop the folder into Caesium and press compress. Keep Meta Data is ON. But also OFF the app crashes. Maybe you can use this test data to figure out the problem. After the failed compression, temporary Images caesium made during compression remain in the folder. |
@Ghost007 can confirm it crashes during compression. Problem seems related to the underneath library and some kind of "bogus colorspace". |
#98 (comment) fixed in v2.0.0-rc.1 |
Just tested v2.0.0 BETA3 under WINDOWS 10 64 BIT 21H1 OS build 19043.1466. It crashed during working and left behind an empty output temporary file (When you are asking why I use the BEAT instead of the V 1.7.0 the reason is that V 1.7.0 recently started hanging in the file chooser dialog).
V2.0.0 BETA 3 works as expected when file to be compressed and output folder both reside on the system drive. However when the file to be compressed resides on a different drive, then the app crashes (I tested this with two different drives.)
The text was updated successfully, but these errors were encountered: