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
Thank you for the report, but I'm afraid that this won't be fixed.
Once started, compression can fail due to several different reasons - normal and abnormal. Normal reasons include I/O error, out of disk space, insufficient memory etc. In all these cases output file should be removed upon exit, as expected.
However assertion error (such as #14) means a bug in the code. When such abnormal condition occurs, the program is aborted immediately without any cleanup and core is dumped to allow debugging. This is by design and it won't be changed. The right thing is fixing the original bug, not working it around.
Using 2.3, when #14 happens, the bz2 file is not deleted:
The text was updated successfully, but these errors were encountered: