Bug 230401

Summary: MSVC++ Runtime error on large TIFs with layers
Product: [Applications] digikam Reporter: francois
Component: Plugin-DImg-TIFFAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: ahuggel, caulier.gilles, francois, Julien
Priority: NOR    
Version: 1.1.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In: 5.0.0
Sentry Crash Report:
Attachments: attachment-23013-0.html

Description francois 2010-03-12 03:13:58 UTC
Version:           1.1.0 (using KDE 4.4.0)
OS:                MS Windows
Installed from:    MS Windows

I get the following message: "C:\...\digikam.exe
This application has requested the Runtime to terminate in ana unusual way..."

This happens when I scan an album where there are large, layered TIFs. A 215MB TIF is OK, but one that is 236MB is not (both with layers, both 8 bit per channel). A TIF of 266MB with no layer (well, only one technically speaking) scans OK, whether in 8 or 16 bit.
Comment 1 francois 2010-03-12 03:16:52 UTC
Note: Digikam also crashes predictably on a 116MB layered TIF (2 layers).
Comment 2 caulier.gilles 2010-03-12 09:47:52 UTC
About crash, a backtrace will be suitable...

Which libtiff and Exiv2 version you use ? Go to Help/components info for details

Gilles Caulier
Comment 3 francois 2010-03-12 17:37:10 UTC
Thanks Gilles. I still have to learn about getting a backtrace under Windows... I appreciate this is not ideal for you.

libtiff3.dll is version 3.8.2.2278. There is a libtiff library that comes with Nikon Capture NX2, but I suppose that's not what you are after.

"Exiv2 -V" reports 2.0.18.1
Comment 4 francois 2010-03-13 00:38:04 UTC
Missed the comment about Help/Components info... Here it is:

digiKam version 1.1.0
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: No
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibExiv2: 0.18.1
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.4.00 (KDE 4.4.0)
LibKExiv2: 1.0.0
LibKdcraw: 1.0.0
LibLCMS: 118
LibPGF: 6.09.44
LibPNG: 1.2.35
LibQt: 4.6.1
LibRaw: 0.8.5
LibTIFF: LIBTIFF, Version 3.8.2 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble widget: 0.9
Parallelized demosaicing: No
LibKipi: 1.0.0
Comment 5 Andreas Huggel 2010-03-13 05:36:44 UTC
Francois,

Upgrade to exiv2 from current trunk if at all possible (see http://www.exiv2.org/download.html#devel) and please report back if you run into problems compiling it with MSVC - that compiler gets used a bit less than others during the development cycle. Chances are that will fix the problem.
Note that you'll need to also re-compile digiKam and friends, in particular libkexiv2.

Andreas
Comment 6 francois 2010-03-13 16:45:08 UTC
Thanks Andreas. The reason I use the MSVC-compiled version is that the other versions fail to install correctly on multi-core processors (missing libgomp.dll). That's another problem altogether.

Will look at how to install the MSVC development environment.
Comment 7 francois 2010-03-21 23:59:36 UTC
Andreas,

I must give up on the idea to build Digikam on a multi-processor Win32 platform (which is all I have). I am throwing the towel after days of trying to figure out why emerge wants to download non-existent source files, and after finding out Digikam cannot be built on my platform and no fix is in sight (http://mail.kde.org/pipermail/kde-windows/2010-March/004756.html). 

Hopefully someone else can take on the task of integrating the Exiv2 0.19 into Digikam.
Comment 8 caulier.gilles 2010-04-04 10:46:56 UTC
digiKam and Kipi-plugins 1.2.0 are out. Please check if crash is still valid there.

Thanks in advance

Gilles Caulier
Comment 9 caulier.gilles 2010-10-06 15:05:40 UTC
Exiv2 will never included in digiKam. it compile fine under windows using Cmake.

Look on my tutorial there :

http://www.digikam.org/drupal/node/525

.. And replace Mingw32 by TDM-GCC compiler :

http://tdm-gcc.tdragon.net/

...because i not yet updated my tutorial with this version of GCC for windows.

Gilles Caulier
Comment 10 caulier.gilles 2010-11-24 09:07:40 UTC
digiKam 1.6.0 is out:

http://www.digikam.org/drupal/node/550

Please update and check if this entry still valid.

Thanks in advance

Gilles Caulier
Comment 11 Julien Narboux 2010-12-30 09:31:57 UTC
Can you please test with digikam 1.7.0 if bug is still there ?
There is an installer available here:
http://sourceforge.net/projects/digikam/files/digikam/1.7.0/digiKam-installer-1.7-win32.exe/download

Julien
Comment 12 caulier.gilles 2011-07-03 14:34:56 UTC
With digiKam 2.0.0 RC for windows, problem still here ?

Gilles Caulier
Comment 13 caulier.gilles 2015-07-03 06:01:36 UTC
New digiKam 4.11.0 is available.

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier
Comment 14 francois 2015-07-03 09:52:29 UTC
Created attachment 93468 [details]
attachment-23013-0.html

I'll check when the Windows installer becomes available. I will have a
look at the repository on a regular basis.

On 2015-07-03 07:01, Gilles Caulier wrote:
> https://bugs.kde.org/show_bug.cgi?id=230401
>
> --- Comment #13 from Gilles Caulier <caulier.gilles@gmail.com> ---
> New digiKam 4.11.0 is available.
>
> https://www.digikam.org/node/740
>
> Can you reproduce the problem with this release ?
>
> Gilles Caulier
>
Comment 15 caulier.gilles 2015-07-06 07:39:24 UTC
digiKam 4.11.0 Windows installer is available for download :

http://download.kde.org/stable/digikam/digiKam-installer-4.11.0-win32.exe.mirrorlist
Comment 16 caulier.gilles 2016-05-28 18:24:01 UTC
With next digiKam 5.0.0, we will provide a fully cross-compiled version Windows under Linux where a lots of problems have been fixed.

https://www.flickr.com/photos/digikam/27033685570/in/dateposted-public/

The Windows installer is available here to test :

https://drive.google.com/open?id=0B7yq-xFihT0_SzhxVzF1RDhPbFE

Gilles Caulier