Created attachment 200995 [details]
tiff file causing baloo_file_extractor and gwenview to hang
baloo_file_extractor hangs on the attached tiff file, consuming 100% cpu and making no progress.
gwenview does the same.
Gimp seems to be hanging also... So I expect there is something fishy in libtiff.
Over to maintainer of graphics/tiff.
Please report the issue upstream, and let us know if there is a patch.
It looks to be a corrupt TIFF file, as tiffdump(1) says:
Magic: 0x4d4d <big-endian> Version: 0x2a <ClassicTIFF>
Directory 0: offset 8 (0x8) next 18612227 (0x11c0003)
data/tu_logo.tiff: Error while reading directory count.
That "next" offset looks pretty bogus (and is beyond end-of-file anyway). None of my applications -- gwenview or kolourpaint -- seem to have TIFF support. They don't attempt to show anything, and don't hang or cause high CPU load either. Is that a configuration option somewhere? I **do** have graphics/tiff installed.
Hmmm, the file is 25 years old, and at that time it was usable.
In any case, libtiff should not just choke on it.
Reported upstream as https://github.com/Exiv2/exiv2/issues/715
Tested and found working with exiv2 0.25 and 0.27, so we'll wait for the exiv2 update which is in the pipeline to resolve this.
A commit references this bug:
Date: Sun Mar 17 13:15:01 UTC 2019
New revision: 496059
graphics/exiv2: update to 0.27
- All depending ports have been bumped.
- graphics/py-exiv2 has been marked broken; use graphics/gexiv2 for python bindings
Exp-run by: antoine
exiv2 has now been updated to 0.27 -- could you please check if the issue still occurs?
It is working now.
Thank you for your support!