crash when loading a specific tif file using the option 'DPI from file'

not reproduced when I load the attached file lighthouse.tif, using the same options as above.

the crash appears to be related to the resolution information embedded in the file.

for the file lighthouse.tif, the resolution is reported as 72dpi in Windows Explorer, and the file image-resolution.cpp in the routine readmagick() reports image.xResolution() = 72 as expected.

for the file choppoint_logo.tif, the resolution is reported as 300dpi in Windows Explorer, and the crash occurs somewhere in the routine ImageResolution::readmagick(char const *fn).

No crash with Inkscape 0.91+devel r14058 on OS X 10.7.5, but this error message on the console (the image otherwise opens ok):

** (inkscape:90484): WARNING **: ImageResolution::readmagick: Unknown error

Current Inkscape trunk build uses ImageMagick 6.9.0 (which has tiff 4.0.3 as dependency).

Clarification wrt tests on OS X:

1) The file 'choppoint_logo.tif' imports without warning or other error messages, using ImageMagick successfully to read the image resolution (300dpi)).

2) The file 'lighthouse.tif' imports successfully but fails to retrieve the image resolution from the file due to the mentioned ImageMagick error:
** (inkscape:33911): WARNING **: ImageResolution::readmagick: Unknown error

Opening 'lighthouse.tif' directly with ImageMagick's 'display' command reveals this information:
display: Incompatible type for "FileSource"; tag ignored. `TIFFFetchNormalTag' @ warning/tiff.c/TIFFWarnings/878.
display: Incompatible type for "SceneType"; tag ignored. `TIFFFetchNormalTag' @ warning/tiff.c/TIFFWarnings/878.

Not reproduced on Crunchbang Waldorf, Inkscape trunk rev. 14120. Both TIFF files load correctly, with no console message.

Crash reproduced on Windows XP (32bits), Inkscape trunk rev. 14142.

The win32 devlibs version of ImageMagick is rather old (6.5.9, 2010-01-01) and recent versions seem to fix some TIFF related bugs (see http://www.imagemagick.org/script/changelog.php).

On Crunchbang Waldorf, the Image Magick package is 6.7.7.10.

The issue is not due to Inkscape itself, but to ImageMagick, and more precisely to how it was compiled in our devlibs (exceptions are not correctly handled).

I'm going to take a look at GraphicsMagick to see if it compiles correctly on Windows. I'm quite sure that we don't use recent IM features and thus the GM API should be compatible with our code (via Magick++).

I can no longer reproduce this on Windows 10, Inkscape 1.0alpha (9cedb1b, 2019-02-08)