Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Windows regression: tiff2vips: read error #4496

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

Open
CrispinStichartFNSB opened this issue May 4, 2025 · 1 comment
Open

Windows regression: tiff2vips: read error #4496

CrispinStichartFNSB opened this issue May 4, 2025 · 1 comment
Labels

Comments

@CrispinStichartFNSB
Copy link

Bug report

Describe the bug

Under Windows, 8.16.1 crashes on some images with tiff2vips: read error.

To Reproduce
Steps to reproduce the behavior:

  1. Use Image tif_crash.zip
  2. Use Windows build of libvips 8.16.1
  3. Try to do anything with the provided .tif file, e.g. vips copy crash.tif test.png

Expected behavior
It won't crash.

Actual behavior
It crashes. Last few lines of output:

(vips.exe:32984): VIPS-WARNING **: 08:39:42.143: Premature EOL at line 12598 of strip 0 (got 0, expected 13800)

(vips.exe:32984): VIPS-WARNING **: 08:39:42.150: error in tile 0 x 12592
tiff2vips: read error

The Premature EOL may be related or it may be red herring -- on Linux, 8.16.1 can process the image without crashing, but it produces a bunch of those Premature EOL/Premature EOF warnings.

Environment
(please complete the following information)

  • OS: Windows 11
  • Vips: 8.16.1

Additional context
This is a regression from 8.15.3, which is able to process the image.

@kleisauke
Copy link
Member

This is the same libtiff 4.7.0 incompatibility issue as #4317 (reported upstream at https://gitlab.com/libtiff/libtiff/-/issues/657), which was fixed in PR #4331 and will be included in the forthcoming libvips 8.17 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants