1.4.5: XnViewMP hangs when saving TIF with LZW+Predictor

Reported bugs that have been closed and/or resolved

Moderators: helmut, XnTriq, xnview, Dreamer

Post Reply
User avatar
mpy
Posts: 21
Joined: Thu May 29, 2014 3:31 pm

1.4.5: XnViewMP hangs when saving TIF with LZW+Predictor

Post by mpy »

XnView MP Linux
Version 1.4.5 64bits (May 10 2023)
Libformat version 7.143

OS: Linux / Arch


When using the LZW+Predictor method for saving color TIF images, the saving hangs XnViewMP and corrupts the saved file. Other methods (LZW, ZIP, ...) work fine.

Effect: Program hangs, files are corrupted

To reproduce:
1. Settings -> Formats -> Write -> TIFF: Set "compression for color picture" to "LZW + Predictor"
2. Open an arbitrary (color) image
3. Save this image in TIF Format

Actual behaviour (bug): Saving dialog appears, but does never complete, program hangs until killed. Resulting TIF-File is corrupt; if you use "Save" to update an existing TIF file this file gets destroyed :bug:

Expected behaviour: Saving is done correctly.
User avatar
xnview
Author of XnView
Posts: 46236
Joined: Mon Oct 13, 2003 7:31 am
Location: France
Contact:

Re: 1.4.5: XnViewMP hangs when saving TIF with LZW+Predictor

Post by xnview »

:bugconfirmed: Thanks to your detailed description I can reproduce the problem.
Pierre.
User avatar
xnview
Author of XnView
Posts: 46236
Joined: Mon Oct 13, 2003 7:31 am
Location: France
Contact:

Re: 1.4.5: XnViewMP hangs when saving TIF with LZW+Predictor

Post by xnview »

This problem is supposed to be fixed in XnView MP 1.5.0 beta. Please check and confirm the bug fix here.
Pierre.
User avatar
mpy
Posts: 21
Joined: Thu May 29, 2014 3:31 pm

Re: 1.4.5: XnViewMP hangs when saving TIF with LZW+Predictor

Post by mpy »

Thanks, I tested the Windows version. Bug fixed :D
I'll test the Linux version (where I originally observed the bug) as soon it is available.
User avatar
mpy
Posts: 21
Joined: Thu May 29, 2014 3:31 pm

Re: 1.4.5: XnViewMP hangs when saving TIF with LZW+Predictor

Post by mpy »

I can confirm that this bug is also fixed in the Linux version 1.5.0, thanks :D
Post Reply