[Bug 307602] New: digiKam crashes, when starting up with minimum pic numerbs

[Axel Krebs]

https://bugs.kde.org/show_bug.cgi?id=307602

            Bug ID: 307602
          Severity: crash
           Version: 2.8.0
          Priority: NOR
          Assignee: [hidden email]
           Summary: digiKam crashes,  when starting up with minimum pic
                    numerbs
    Classification: Unclassified
                OS: Linux
          Reporter: [hidden email]
          Hardware: Ubuntu Packages
            Status: UNCONFIRMED
         Component: general
           Product: digikam

Application: digikam (2.8.0)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-31-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Potential [Bug 307275] digiKam crash after long "throttling-phase"

I was creating a _new_ thumbnail database with just three most recent
subfolders.

Selecting "tiff-pic" in order not to se other filetypes.

There are some extrem large tiffs up to 1,8 GB, produced by HUGIN, too large
for ending...

When clicking on a tiff-pic, it crashes.

Questions:
1.) is there a basic start-up modus as we know from other progs (or OSs ) for
safe start?
2.) how to safe any setting  in a file?

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
[Current thread is 1 (Thread 0x7f4d2e6c4840 (LWP 6573))]

Thread 8 (Thread 0x7f4d08be0700 (LWP 6574)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f4d28b274db in wait (time=18446744073709551615, this=0x1c7db20) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x1c7da18,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00000000005d6a30 in Digikam::ScanController::run (this=0x1c7d7b0) at
/build/buildd/digikam-2.8.0/core/digikam/database/scancontroller.cpp:698
#4  0x00007f4d28b26fcb in QThreadPrivate::start (arg=0x1c7d7b0) at
thread/qthread_unix.cpp:298
#5  0x00007f4d1e658b74 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#6  0x00007f4d2350fe9a in start_thread (arg=0x7f4d08be0700) at
pthread_create.c:308
#7  0x00007f4d27d534bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x0000000000000000 in ?? ()

Thread 7 (Thread 0x7f4d03fff700 (LWP 6575)):
#0  0x00007f4d27d47b03 in __GI___poll (fds=<optimized out>, nfds=<optimized
out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f4d2115f036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f4d2115f164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f4d28c55426 in QEventDispatcherGlib::processEvents
(this=0x7f4cfc0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f4d28c24c82 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f4d28c24ed7 in QEventLoop::exec (this=0x7f4d03ffec50, flags=...) at
kernel/qeventloop.cpp:204
#6  0x00007f4d28b23fa7 in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:501
#7  0x00007f4d28c049ff in QInotifyFileSystemWatcherEngine::run (this=0x1ba5280)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f4d28b26fcb in QThreadPrivate::start (arg=0x1ba5280) at
thread/qthread_unix.cpp:298
#9  0x00007f4d1e658b74 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#10 0x00007f4d2350fe9a in start_thread (arg=0x7f4d03fff700) at
pthread_create.c:308
#11 0x00007f4d27d534bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 6 (Thread 0x7f4d022ff700 (LWP 6578)):
#0  0x00007f4d27d47b03 in __GI___poll (fds=<optimized out>, nfds=<optimized
out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f4d2115f036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f4d2115f164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f4d28c55426 in QEventDispatcherGlib::processEvents
(this=0x7f4cf80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f4d28c24c82 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f4d28c24ed7 in QEventLoop::exec (this=0x7f4d022fec50, flags=...) at
kernel/qeventloop.cpp:204
#6  0x00007f4d28b23fa7 in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:501
#7  0x00007f4d28c049ff in QInotifyFileSystemWatcherEngine::run (this=0x67ea8d0)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f4d28b26fcb in QThreadPrivate::start (arg=0x67ea8d0) at
thread/qthread_unix.cpp:298
#9  0x00007f4d1e658b74 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#10 0x00007f4d2350fe9a in start_thread (arg=0x7f4d022ff700) at
pthread_create.c:308
#11 0x00007f4d27d534bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f4cdbfff700 (LWP 6617)):
[KCrash Handler]
#6  0x00007f4d2bd64933 in Digikam::TIFFLoader::load (this=0x7f4cdbffdc30,
filePath=..., observer=0x159a44f0) at
/build/buildd/digikam-2.8.0/core/libs/dimg/loaders/tiffloader.cpp:638
#7  0x00007f4d2bd3facd in Digikam::DImg::load (this=0x7f4cdbffe3a0,
filePath=..., loadFlagsInt=13, observer=0x159a44f0, rawDecodingSettings=...) at
/build/buildd/digikam-2.8.0/core/libs/dimg/dimg.cpp:451
#8  0x00007f4d2bd4118e in Digikam::DImg::load (this=0x7f4cdbffe3a0,
filePath=..., loadMetadata=<optimized out>, loadICCData=<optimized out>,
loadUniqueHash=<optimized out>, loadImageHistory=<optimized out>,
observer=0x159a44f0, rawDecodingSettings=...) at
/build/buildd/digikam-2.8.0/core/libs/dimg/dimg.cpp:406
#9  0x00007f4d2bf25488 in Digikam::ThumbnailCreator::loadWithDImg
(this=0x662a280, path=..., profile=0x7f4cdbffe560) at
/build/buildd/digikam-2.8.0/core/libs/threadimageio/thumbnailcreator.cpp:561
#10 0x00007f4d2bf25fcb in Digikam::ThumbnailCreator::createThumbnail
(this=0x662a280, info=..., detailRect=..., isFace=false) at
/build/buildd/digikam-2.8.0/core/libs/threadimageio/thumbnailcreator.cpp:490
#11 0x00007f4d2bf26630 in Digikam::ThumbnailCreator::load (this=0x662a280,
path=..., rect=..., pregenerate=true) at
/build/buildd/digikam-2.8.0/core/libs/threadimageio/thumbnailcreator.cpp:260
#12 0x00007f4d2bf27a2d in Digikam::ThumbnailCreator::pregenerate
(this=<optimized out>, path=...) at
/build/buildd/digikam-2.8.0/core/libs/threadimageio/thumbnailcreator.cpp:183
#13 0x00007f4d2bf36120 in Digikam::ThumbnailLoadingTask::execute
(this=0x159a44e0) at
/build/buildd/digikam-2.8.0/core/libs/threadimageio/thumbnailtask.cpp:80
#14 0x00007f4d2bf05b5e in Digikam::LoadSaveThread::run (this=0x662e9d0) at
/build/buildd/digikam-2.8.0/core/libs/threadimageio/loadsavethread.cpp:136
#15 0x00007f4d2bf4832e in Digikam::DynamicThread::DynamicThreadPriv::run
(this=0x664e940) at
/build/buildd/digikam-2.8.0/core/libs/threads/dynamicthread.cpp:186
#16 0x00007f4d28b1a4f2 in QThreadPoolThread::run (this=0x1541dc50) at
concurrent/qthreadpool.cpp:107
#17 0x00007f4d28b26fcb in QThreadPrivate::start (arg=0x1541dc50) at
thread/qthread_unix.cpp:298
#18 0x00007f4d1e658b74 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#19 0x00007f4d2350fe9a in start_thread (arg=0x7f4cdbfff700) at
pthread_create.c:308
#20 0x00007f4d27d534bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#21 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f4ce2586700 (LWP 6618)):
#0  0x00007f4d23e923d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#1  0x00007f4d23e90efe in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#2  0x00007f4d1e658b74 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#3  0x00007f4d2350fe9a in start_thread (arg=0x7f4ce2586700) at
pthread_create.c:308
#4  0x00007f4d27d534bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f4ce1d85700 (LWP 6619)):
#0  0x00007f4d23e923d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#1  0x00007f4d23e90efe in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#2  0x00007f4d1e658b74 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#3  0x00007f4d2350fe9a in start_thread (arg=0x7f4ce1d85700) at
pthread_create.c:308
#4  0x00007f4d27d534bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f4ce1584700 (LWP 6620)):
#0  0x00007f4d23e923d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#1  0x00007f4d23e90efe in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1
#2  0x00007f4d1e658b74 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#3  0x00007f4d2350fe9a in start_thread (arg=0x7f4ce1584700) at
pthread_create.c:308
#4  0x00007f4d27d534bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f4d2e6c4840 (LWP 6573)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f4d28b274db in wait (time=18446744073709551615, this=0x1f1c6c0) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x1b0fa98,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f4d28b19c7e in QThreadPoolPrivate::waitForDone (this=0x1b0fa10,
msecs=-1) at concurrent/qthreadpool.cpp:298
#4  0x00007f4d28b1b6a4 in QThreadPool::~QThreadPool (this=0x1d371c0,
__in_chrg=<optimized out>) at concurrent/qthreadpool.cpp:440
#5  0x00007f4d28b1b6e9 in QThreadPool::~QThreadPool (this=0x1d371c0,
__in_chrg=<optimized out>) at concurrent/qthreadpool.cpp:442
#6  0x00007f4d28c38935 in QObjectPrivate::deleteChildren (this=0x1b27950) at
kernel/qobject.cpp:1908
#7  0x00007f4d28c3eb9c in QObject::~QObject (this=0x1b118f0,
__in_chrg=<optimized out>) at kernel/qobject.cpp:927
#8  0x00007f4d2bf458c7 in ~ThreadManagerCreator (this=0x1b118f0,
__in_chrg=<optimized out>) at
/build/buildd/digikam-2.8.0/core/libs/threads/threadmanager.cpp:236
#9  destroy () at
/build/buildd/digikam-2.8.0/core/libs/threads/threadmanager.cpp:241
#10 0x00007f4d27c9c921 in __run_exit_handlers (status=1, listp=0x7f4d28017688,
run_list_atexit=true) at exit.c:78
#11 0x00007f4d27c9c9a5 in __GI_exit (status=<optimized out>) at exit.c:100
#12 0x00007f4d2968b5e8 in qt_xio_errhandler () at
kernel/qapplication_x11.cpp:780
#13 0x00007f4d2a3576b8 in KApplication::xioErrhandler (this=0x7fffe35c9030,
dpy=0x1a9c520) at ../../kdeui/kernel/kapplication.cpp:419
#14 0x00007f4d2626441e in _XIOError () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#15 0x00007f4d26261e1d in _XEventsQueued () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#16 0x00007f4d2625342f in XEventsQueued () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#17 0x00007f4d296c7b9c in x11EventSourceCheck (s=0x1a8b100) at
kernel/qguieventdispatcher_glib.cpp:85
#18 0x00007f4d2115eb43 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f4d2115efd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f4d2115f164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f4d28c553bf in QEventDispatcherGlib::processEvents (this=0x1a1fb30,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#22 0x00007f4d296c7d5e in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007f4d28c24c82 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#24 0x00007f4d28c24ed7 in QEventLoop::exec (this=0x7fffe35c8eb0, flags=...) at
kernel/qeventloop.cpp:204
#25 0x00007f4d28c29f67 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1148
#26 0x000000000048f63b in main (argc=1, argv=<optimized out>) at
/build/buildd/digikam-2.8.0/core/digikam/main/main.cpp:232

This bug may be a duplicate of or related to bug 295020.

Possible duplicates by query: bug 307275, bug 307119, bug 307013, bug 306492,
bug 301122.

Reported using DrKonqi

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Axel Krebs]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #1 from Axel Krebs <[hidden email]> ---
Created attachment 74240
  --> https://bugs.kde.org/attachment.cgi?id=74240&action=edit
large tiff mkes digiKam crash?

Some thoughts:
1.) the pic remained on my PC when HUGIN maks new panorama-pics.
These panorama pics can reach up to 1 GB when finshed.
Don't know, if these intermediate pics follow tiff definitions!?
Don't know, why these püic rmains sometimes on the PC

2.) I wonder, if a size limit would resolve the problems I face(d?)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Axel Krebs]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #2 from Axel Krebs <[hidden email]> ---
Question / Suggestion:

Maybe it is a good idea to check pics (intermediatly and) continously in
background.

GIMP does _not_ crash when opening such huge pics

Maybe there is no such effective error handling in digiKam?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #3 from Gilles Caulier <[hidden email]> ---
Ok,

Now as you have isolated the tiff file which crash digiKam please share this
TIFF with us to test in local. Please use a share free space on the web...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Axel Krebs]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #4 from Axel Krebs <[hidden email]> ---
sorry, can't find working free space- space limits, wheras file has 1.7GB

"minus-com"/"sendspace.com" won't work

Idea?


Axel
---
Am 30.09.2012 12:51, schrieb Gilles Caulier:

> https://bugs.kde.org/show_bug.cgi?id=307602
>
> Gilles Caulier <[hidden email]> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |[hidden email]
>
> --- Comment #3 from Gilles Caulier <[hidden email]> ---
> Ok,
>
> Now as you have isolated the tiff file which crash digiKam please share this
> TIFF with us to test in local. Please use a share free space on the web...
>
> Gilles Caulier
>

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #5 from Gilles Caulier <[hidden email]> ---
Cut file with rar archover and use a decent files sharing service. "uptobox"
for ex is very fast

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Axel Krebs]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #6 from Axel Krebs <[hidden email]> ---
Am 30.09.2012 14:07, schrieb Gilles Caulier:
> Gilles Caulier
I didn't get it... if you don't mind, let me send you a DVD to a
_postal_ address.


Axel

(> [hidden email])

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #7 from Gilles Caulier <[hidden email]> ---
Hum, it a tol complicated way.

How do to generate this huge TIFF file ? With hugin ? If yes, if original files
are JPEG, it's more easy to share it, and let's me to regenerate TIFF with
hugin. Right ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Axel Krebs]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #8 from Axel Krebs <[hidden email]> ---
Am 01.10.2012 23:13, schrieb Gilles Caulier:

> https://bugs.kde.org/show_bug.cgi?id=307602
>
> --- Comment #7 from Gilles Caulier <[hidden email]> ---
> Hum, it a tol complicated way.
>
> How do to generate this huge TIFF file ? With hugin ? If yes, if original files
> are JPEG, it's more easy to share it, and let's me to regenerate TIFF with
> hugin. Right ?
>
> Gilles Caulier
>

thanks for answer!

You want to reproduce the huge files with HUGIN directly?

As much as I see, sometimes I get those file sizes... sometimes, HUGIN
does no erase intermediate files, and the huge files seem to be such
remainings...

(P.S.: HUGIN: 2011.4.0.cf9be9344356)

Original pics are DSC_4052 .. DSC_4063: 12 pics, minimum size 3,7 MB,
Max 5.5 MB, together 53,2MB. with my sleepery connection, this would
take forever...

Shall we try reproduce HUGINs behavior or resolve digiKams crashes?

Why not sending a DVD with two huge TIF-files _and_ the 12 original JPGs?

The DVD is burned already...



Axel

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|digiKam crashes,  when      |Large TIFF files crash
                   |starting up with minimum    |digiKam (>1Gb)
                   |pic numerbs                 |

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #9 from Gilles Caulier <[hidden email]> ---
We must to understand if hugin tiff generator make something wrong, and found
the problem in digiKam TIFF loader.

If you want to send me a DVD why not. My mail adress is :

Gilles Caulier, 16 Impasse de la Cascade, 13770 Venelles, France.

Gilles

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #10 from Gilles Caulier <[hidden email]> ---
Marcel,

I just recieve DVD from Alex with Large tiff files. Problem is fully
reproducible with digiKam 3.0.0 :

digikam(22522)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation =>
Exif.Image.Orientation =>  8
digikam(22522)/digikam (core) Digikam::DMetadata::getImageHistory: Loading
image history  ""
digikam(22522)/digikam (core) Digikam::ImageScanner::commit: Scanning took 10
ms
digikam(22522)/digikam (core) Digikam::ImageScanner::~ImageScanner: Finishing
took 3 ms
digikam(22522)/digikam (core)
Digikam::CollectionScanner::completeHistoryScanning: items to tag ()
digikam(22522)/digikam (core) Digikam::DImg::load: "/mnt/data/photos/TESTS/Alex
Krebs/DSC_4052-DSC_40630004.tif"  : TIFF file identified
KCrash: Application 'digikam' crashing...

Thread 5 (Thread 0x7f8d56605700 (LWP 22562)):
[KCrash Handler]
#6  0x00007f8d8e5e5b0a in Digikam::TIFFLoader::load (this=0x7f8d56603f70,
filePath=..., observer=0x306d580) at
/mnt/devel/GIT/3.x/core/libs/dimg/loaders/tiffloader.cpp:548
#7  0x00007f8d8e5ae7a0 in Digikam::DImg::load (this=0x7f8d566043f0,
filePath=..., loadFlagsInt=13, observer=0x306d580, rawDecodingSettings=...) at
/mnt/devel/GIT/3.x/core/libs/dimg/dimg.cpp:449
#8  0x00007f8d8e5ae21e in Digikam::DImg::load (this=0x7f8d566043f0,
filePath=..., loadMetadata=false, loadICCData=true, loadUniqueHash=false,
loadImageHistory=false, observer=0x306d580, rawDecodingSettings=...) at
/mnt/devel/GIT/3.x/core/libs/dimg/dimg.cpp:403
#9  0x00007f8d8e78eacb in Digikam::ThumbnailCreator::loadWithDImg
(this=0x255de30, path=..., profile=0x7f8d566044c0) at
/mnt/devel/GIT/3.x/core/libs/threadimageio/thumbnailcreator.cpp:561
#10 0x00007f8d8e78e2d9 in Digikam::ThumbnailCreator::createThumbnail
(this=0x255de30, info=..., detailRect=..., isFace=false) at
/mnt/devel/GIT/3.x/core/libs/threadimageio/thumbnailcreator.cpp:490
#11 0x00007f8d8e78ce99 in Digikam::ThumbnailCreator::load (this=0x255de30,
path=..., rect=..., pregenerate=false) at
/mnt/devel/GIT/3.x/core/libs/threadimageio/thumbnailcreator.cpp:260
#12 0x00007f8d8e78cac8 in Digikam::ThumbnailCreator::load (this=0x255de30,
path=...) at
/mnt/devel/GIT/3.x/core/libs/threadimageio/thumbnailcreator.cpp:199
#13 0x00007f8d8e79b7ac in Digikam::ThumbnailLoadingTask::execute
(this=0x306d570) at
/mnt/devel/GIT/3.x/core/libs/threadimageio/thumbnailtask.cpp:170
#14 0x00007f8d8e776ae1 in Digikam::LoadSaveThread::run (this=0x255db70) at
/mnt/devel/GIT/3.x/core/libs/threadimageio/loadsavethread.cpp:136
#15 0x00007f8d8e7a2960 in Digikam::DynamicThread::DynamicThreadPriv::run
(this=0x255dbe0) at /mnt/devel/GIT/3.x/core/libs/threads/dynamicthread.cpp:186
#16 0x00007f8d89aa74a2 in ?? () from /usr/lib64/libQtCore.so.4
#17 0x00007f8d89ab3c3b in ?? () from /usr/lib64/libQtCore.so.4
#18 0x00007f8d89823b99 in start_thread () from /lib64/libpthread.so.0
#19 0x00007f8d888550cd in clone () from /lib64/libc.so.6
#20 0x0000000000000000 in ?? ()

Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.23
LibJPEG: 80
LibJasper: 1.900.1
LibKDE: 4.8.5 (4.8.5)
LibKExiv2: 2.3.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.2.0
LibLCMS: 119
LibLensFun: external shared library
LibLqr: internal library
LibPGF: 6.11.42 - external shared library
LibPNG: 1.5.10
LibQt: 4.8.2
LibRaw: 0.15.0-Alpha4
LibTIFF: LIBTIFF, Version 4.0.1 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.13.4 (stable release)
Parallelized PGF codec: No
Parallelized demosaicing: Yes
RawSpeed codec support: Yes

[gilles@localhost core (master)]$ ls -al "/mnt/data/photos/TESTS/Alex Krebs/"
total 5128152
drwxrwxr-x  3 gilles gilles       4096 oct.  11 13:55 ./
drwxr-xr-x 46 gilles gilles       4096 oct.  11 13:46 ../
-r--r--r--  1 gilles gilles   16614150 sept. 18 07:06 DSC_4052-DSC_40630000.tif
-r--r--r--  1 gilles gilles   32852286 sept. 18 07:06 DSC_4052-DSC_40630001.tif
-r--r--r--  1 gilles gilles 1477235108 sept. 18 07:18 DSC_4052-DSC_40630002.tif
-r--r--r--  1 gilles gilles 1698042226 sept. 18 07:27 DSC_4052-DSC_40630003.tif
-r--r--r--  1 gilles gilles 1823832214 sept. 18 07:37 DSC_4052-DSC_40630004.tif
-r--r--r--  1 gilles gilles  100241338 sept. 18 07:38 DSC_4052-DSC_40630005.tif
-r--r--r--  1 gilles gilles   26953084 sept. 18 07:38 DSC_4052-DSC_40630006.tif
-r--r--r--  1 gilles gilles   22224704 sept. 18 07:38 DSC_4052-DSC_40630007.tif
-r--r--r--  1 gilles gilles    5217105 sept. 16 13:04 DSC_4052.JPG
-r--r--r--  1 gilles gilles    5172771 sept. 16 13:04 DSC_4053.JPG
-r--r--r--  1 gilles gilles    4843119 sept. 16 13:04 DSC_4054.JPG
-r--r--r--  1 gilles gilles    4670839 sept. 16 13:04 DSC_4055.JPG
-r--r--r--  1 gilles gilles    4480745 sept. 16 13:04 DSC_4056.JPG
-r--r--r--  1 gilles gilles    4489894 sept. 16 13:04 DSC_4057.JPG
-r--r--r--  1 gilles gilles    4231733 sept. 16 13:04 DSC_4058.JPG
-r--r--r--  1 gilles gilles    4041280 sept. 16 13:04 DSC_4059.JPG
-r--r--r--  1 gilles gilles    4157543 sept. 16 13:04 DSC_4060.JPG
-r--r--r--  1 gilles gilles    4261651 sept. 16 13:04 DSC_4061.JPG
-r--r--r--  1 gilles gilles    3877228 sept. 16 13:04 DSC_4062.JPG
-r--r--r--  1 gilles gilles    3722625 sept. 16 13:04 DSC_4063.JPG
drwxrwxr-x  2 gilles gilles       4096 oct.   3 11:01 screen/
[gilles@localhost core (master)]$

digiKam crash when image DSC_4052-DSC_40630004.tif is parsed (1,7Gb)

This is not an allocation problem on my computer to load image. My i5 Box has
16 Gb or RAM...

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #11 from Gilles Caulier <[hidden email]> ---
identification of image with ImageMagick :

[gilles@localhost core (master)]$ identify -verbose
"/mnt/data/photos/TESTS/Alex Krebs/DSC_4052-DSC_40630004.tif" -version
Image: /mnt/data/photos/TESTS/Alex Krebs/DSC_4052-DSC_40630004.tif
  Format: TIFF (Tagged Image File Format)
  Class: DirectClass
  Geometry: 11939x108859+0+0
  Resolution: 150x150
  Print size: 79.5933x725.727
  Units: PixelsPerInch
  Type: TrueColorMatte
  Base type: TrueColor
  Endianess: MSB
  Colorspace: sRGB
  Depth: 8-bit
  Channel depth:
    red: 8-bit
    green: 8-bit
    blue: 8-bit
    alpha: 1-bit
  Channel statistics:
    Red:
      min: 0 (0)
      max: 255 (1)
      mean: 132.861 (0.521023)
      standard deviation: 94.7031 (0.371385)
      kurtosis: -1.90999
      skewness: -0.0217065
    Green:
      min: 0 (0)
      max: 255 (1)
      mean: 150.436 (0.589946)
      standard deviation: 99.5435 (0.390367)
      kurtosis: -1.90405
      skewness: -0.055626
    Blue:
      min: 0 (0)
      max: 255 (1)
      mean: 154.395 (0.60547)
      standard deviation: 101.835 (0.399353)
      kurtosis: -1.89304
      skewness: -0.0871236
    Alpha:
      min: 0 (0)
      max: 255 (1)
      mean: 247.312 (0.969851)
      standard deviation: 43.6041 (0.170997)
      kurtosis: 28.1999
      skewness: 5.49544
  Image statistics:
    Overall:
      min: 0 (0)
      max: 255 (1)
      mean: 111.345 (0.436647)
      standard deviation: 88.2458 (0.346062)
      kurtosis: -0.166605
      skewness: 0.660303
  Alpha: none   #00000000
  Rendering intent: Perceptual
  Gamma: 0.45455
  Chromaticity:
    red primary: (0.64,0.33)
    green primary: (0.3,0.6)
    blue primary: (0.15,0.06)
    white point: (0.3127,0.329)
  Interlace: None
  Background color: white
  Border color: srgba(223,223,223,1)
  Matte color: grey74
  Transparent color: none
  Compose: Over
  Page geometry: 11939x108859+0+108860
  Origin geometry: +0+108860
  Dispose: Undefined
  Iterations: 0
  Compression: LZW
  Orientation: TopLeft
  Properties:
    date:create: 2012-10-11T13:54:58+02:00
    date:modify: 2012-09-18T07:37:35+02:00
    signature: b1f1e065fc3bd5dd454084b54d283d9e909e73c974f6c29f035f21afb17444d6
    tiff:alpha: unassociated
    tiff:endian: lsb
    tiff:photometric: RGB
    tiff:rows-per-strip: 21
  Artifacts:
    filename: /mnt/data/photos/TESTS/Alex Krebs/DSC_4052-DSC_40630004.tif
    verbose: true
  Tainted: False
  Filesize: 1.8238GB
  Number pixels: 1.2997G
  Pixels per second: 48.23MB
  User time: 25.840u
  Elapsed time: 0:27.950
  Version: ImageMagick 6.7.5-10 2012-08-22 Q16 http://www.imagemagick.org

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #12 from Gilles Caulier <[hidden email]> ---
Marcel,

The crash appears when data are read from tiff and Red and Blue channels are
switched :

                uchar* stripPtr = (uchar*)(strip.data());
                uchar* dataPtr  = (uchar*)(data.data() + offset);
                uchar* p;

                // Reverse red and blue

                for (int i = 0; i < pixelsRead; ++i)
                {
                    p = dataPtr;

                    p[2] = *stripPtr++;              // <========== CRASh here
!
                    p[1] = *stripPtr++;
                    p[0] = *stripPtr++;
                    p[3] = *stripPtr++;

                    dataPtr += 4;
                }

Why ?

Note : If i want to display image with ImageMagick, it crash too !!!


[gilles@localhost core (master)]$ gdb --args display
"/mnt/data/photos/TESTS/Alex Krebs/DSC_4052-DSC_40630004.tif"
GNU gdb (GDB) 7.3.50.20110722-4.mga2 (Mageia release 2)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-mageia-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/display...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/display /mnt/data/photos/TESTS/Alex\
Krebs/DSC_4052-DSC_40630004.tif
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Program received signal SIGBUS, Bus error.
0x00007ffff7a533e0 in SetImageBackgroundColor () from
/usr/lib64/libMagickCore.so.5
(gdb) bt
#0  0x00007ffff7a533e0 in SetImageBackgroundColor () from
/usr/lib64/libMagickCore.so.5
#1  0x00007ffc5168cff6 in ?? () from
/usr/lib64/ImageMagick-6.7.5/modules-Q16/coders/pattern.so
#2  0x00007ffff79d3590 in ReadImage () from /usr/lib64/libMagickCore.so.5
#3  0x00007ffff7b04dd2 in ?? () from /usr/lib64/libMagickCore.so.5
#4  0x00007ffff7b0e70c in XMakeImage () from /usr/lib64/libMagickCore.so.5
#5  0x00007ffff79f9847 in XDisplayImage () from /usr/lib64/libMagickCore.so.5
#6  0x00007ffff76a5810 in DisplayImageCommand () from
/usr/lib64/libMagickWand.so.5
#7  0x00007ffff76f06a1 in MagickCommandGenesis () from
/usr/lib64/libMagickWand.so.5
#8  0x00000000004007e9 in ?? ()
#9  0x00007ffff70be32d in __libc_start_main () from /lib64/libc.so.6
#10 0x0000000000400839 in ?? ()
#11 0x00007fffffffda68 in ?? ()
#12 0x000000000000001c in ?? ()
#13 0x0000000000000002 in ?? ()
#14 0x00007fffffffdedf in ?? ()
#15 0x00007fffffffdef0 in ?? ()
#16 0x0000000000000000 in ?? ()

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #13 from Gilles Caulier <[hidden email]> ---
The image can be loaded in Gimp, but it's really strange... Image is vertically
oriented and completely deformed...

Gilles

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #14 from Gilles Caulier <[hidden email]> ---
Gwenview cannot load image, but do not crash. It report quickly an error in GUI
(nothing in the console). Sound like a simple "no support error", not an image
decoding error....

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #15 from Gilles Caulier <[hidden email]> ---
Important : i see a lots of fee space fully used here :


[gilles@localhost manager (master)]$ df
Sys. fich.               Taille Util. Dispo Uti% Monté sur
rootfs                      30G   29G     0 100% /
devtmpfs                   7,8G     0  7,8G   0% /dev
tmpfs                      7,8G   17M  7,8G   1% /dev/shm
tmpfs                      7,8G  2,9M  7,8G   1% /run
/dev/sda1                   30G   29G     0 100% /
tmpfs                      7,8G     0  7,8G   0% /sys/fs/cgroup
/dev/sda6                  146G   15G  124G  11% /mnt/devel
/dev/sda3                   20G   19G  4,0K 100% /tmp
/dev/sda5                   20G   15G  5,5G  72% /home
/dev/sdd1                  1,9T  508G  1,3T  29% /mnt/data
/dev/mapper/lvm--video-1   5,5T  2,1T  3,2T  40% /mnt/videos
[gilles@localhost manager (master)]$

In fact / and /tmp are full where normally i have a full of free space to
work...

Gilles

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #16 from Gilles Caulier <[hidden email]> ---
In /tmp, IM has make some dirty think :


[root@localhost manager (master)]# du -hms /tmp/* | sort -nr | head
9916    /tmp/magick-l66Ht8cw
8572    /tmp/magick-zlaovCfC
16      /tmp/magick-EkjCOp7E
6       /tmp/kde-gilles
1       /tmp/systemd-namespace-zlJBOl
1       /tmp/systemd-namespace-XYqfQi
1       /tmp/systemd-namespace-X36Tsv
1       /tmp/systemd-namespace-uMQ6Tj
1       /tmp/systemd-namespace-UHtbR2
1       /tmp/systemd-namespace-Q8z6Bu

2 first files are giant (:=))

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #17 from Gilles Caulier <[hidden email]> ---
on /, i can see this :

[root@localhost /]# find . -ls | awk '{printf(" %12d %s \n ",$7 ,$11)}' | sort
-nr | head
  140737486266368 ./proc/kcore

... probably due to memory lost with IM crash...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=307602

--- Comment #18 from Marcel Wiesweg <[hidden email]> ---
All buffers are allocated in lines 461/2:
            data.reset(new_failureTolerant(w * h * 4));
            QScopedArrayPointer<uchar> strip(new_failureTolerant(w *
rows_per_strip * 4));
and checked later.

Does it crash already on the first iteration, or sometime late during the
decoding?
Is it possible to get a valgrind trace?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel