Bug 329824 - digikam crashed when importing photos from SD
Summary: digikam crashed when importing photos from SD
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Albums (show other bugs)
Version: 3.3.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-01-10 20:12 UTC by Johannes Midgren
Modified: 2017-08-16 10:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.0.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Midgren 2014-01-10 20:12:41 UTC
Application: digikam (3.3.0)
KDE Platform Version: 4.12.0
Qt Version: 4.8.2
Operating System: Linux 3.2.0-58-generic x86_64
Distribution: Ubuntu 12.04.3 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was importing photos from an SD card (taken out of my Sony alpha 55). 
The program was unresponsive for a while when scrolling through photos to be downloaded, it then "came back" and showed downloaded thumbnails. When I tried to scroll further down again it crashed.

This has happened to me before - the program becomes unresponsive after thumbnails are/were loaded when importing photos.

- I have enabled the feature to create sub folders based on ISO formatted capture date (not that I think it matters). 
- My database is stored in MySQL on a server (not the same machine as running digikam).

The crash can be reproduced sometimes.

-- Backtrace:
Application: Digikam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f74553b9a00 (LWP 31404))]

Thread 6 (Thread 0x7f742e784700 (LWP 31408)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f744fa575ab in wait (time=18446744073709551615, this=0xe78e60) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0xe78d68, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00000000005e0860 in Digikam::ScanController::run (this=0xe78b00) at /build/buildd/digikam-3.3.0/core/digikam/database/scancontroller.cpp:725
#4  0x00007f744fa5709b in QThreadPrivate::start (arg=0xe78b00) at thread/qthread_unix.cpp:307
#5  0x00007f7449fffe9a in start_thread (arg=0x7f742e784700) at pthread_create.c:308
#6  0x00007f744ec803fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f742df83700 (LWP 31409)):
#0  0x00007f74477b8930 in pthread_mutex_lock@plt () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f74478225b1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f74477e6811 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f74477e6f1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f74477e7124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f744fb85926 in QEventDispatcherGlib::processEvents (this=0x7f74200008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f744fb54e62 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f744fb550b7 in QEventLoop::exec (this=0x7f742df82b50, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f744fa54077 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9  0x00007f744fb34b6f in QInotifyFileSystemWatcherEngine::run (this=0xe5d040) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007f744fa5709b in QThreadPrivate::start (arg=0xe5d040) at thread/qthread_unix.cpp:307
#11 0x00007f7449fffe9a in start_thread (arg=0x7f742df83700) at pthread_create.c:308
#12 0x00007f744ec803fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f742d782700 (LWP 31485)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f744fa575ab in wait (time=18446744073709551615, this=0x12701e0) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x124df58, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f7452b69321 in Digikam::ParkingThread::run (this=0x124df40) at /build/buildd/digikam-3.3.0/core/libs/threads/threadmanager.cpp:119
#4  0x00007f744fa5709b in QThreadPrivate::start (arg=0x124df40) at thread/qthread_unix.cpp:307
#5  0x00007f7449fffe9a in start_thread (arg=0x7f742d782700) at pthread_create.c:308
#6  0x00007f744ec803fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f742c801700 (LWP 31486)):
#0  0x00007f744ec72ffd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f74478218df in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f74477e6b64 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f74477e6f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f74477e7124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f744fb85926 in QEventDispatcherGlib::processEvents (this=0x7f7418000900, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f744fb54e62 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f744fb550b7 in QEventLoop::exec (this=0x7f742c800b50, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f744fa54077 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9  0x00007f744fb34b6f in QInotifyFileSystemWatcherEngine::run (this=0x1b37e40) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007f744fa5709b in QThreadPrivate::start (arg=0x1b37e40) at thread/qthread_unix.cpp:307
#11 0x00007f7449fffe9a in start_thread (arg=0x7f742c801700) at pthread_create.c:308
#12 0x00007f744ec803fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f737da7c700 (LWP 32349)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f744fa575ab in wait (time=18446744073709551615, this=0x11277310) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x1127c0d8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00000000007e10e2 in Digikam::CameraController::run (this=0x1017e7e0) at /build/buildd/digikam-3.3.0/core/utilities/importui/backend/cameracontroller.cpp:389
#4  0x00007f744fa5709b in QThreadPrivate::start (arg=0x1017e7e0) at thread/qthread_unix.cpp:307
#5  0x00007f7449fffe9a in start_thread (arg=0x7f737da7c700) at pthread_create.c:308
#6  0x00007f744ec803fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f74553b9a00 (LWP 31404)):
[KCrash Handler]
#6  Digikam::AlbumManager::removePAlbum (this=0xf62f10, album=0x1281e2d0) at /build/buildd/digikam-3.3.0/core/digikam/album/albummanager.cpp:2825
#7  0x00000000005ba9c1 in Digikam::AlbumManager::scanPAlbums (this=0xf62f10) at /build/buildd/digikam-3.3.0/core/digikam/album/albummanager.cpp:1261
#8  0x00007f744fb6a781 in QMetaObject::activate (sender=0xe5b690, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#9  0x00007f744fb6f679 in QObject::event (this=0xe5b690, e=<optimized out>) at kernel/qobject.cpp:1157
#10 0x00007f74505557b4 in notify_helper (e=0x7fffe4a1ee80, receiver=0xe5b690, this=0xd9bb10) at kernel/qapplication.cpp:4556
#11 QApplicationPrivate::notify_helper (this=0xd9bb10, receiver=0xe5b690, e=0x7fffe4a1ee80) at kernel/qapplication.cpp:4528
#12 0x00007f745055a583 in QApplication::notify (this=0x7fffe4a1f260, receiver=0xe5b690, e=0x7fffe4a1ee80) at kernel/qapplication.cpp:4417
#13 0x00007f745128e0e6 in KApplication::notify (this=0x7fffe4a1f260, receiver=0xe5b690, event=0x7fffe4a1ee80) at ../../kdeui/kernel/kapplication.cpp:311
#14 0x00007f744fb5632c in QCoreApplication::notifyInternal (this=0x7fffe4a1f260, receiver=0xe5b690, event=0x7fffe4a1ee80) at kernel/qcoreapplication.cpp:915
#15 0x00007f744fb876f2 in sendEvent (event=0x7fffe4a1ee80, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#16 QTimerInfoList::activateTimers (this=0xd9ce60) at kernel/qeventdispatcher_unix.cpp:611
#17 0x00007f744fb8510d in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#18 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#19 0x00007f74477e6d13 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f74477e7060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f74477e7124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f744fb858bf in QEventDispatcherGlib::processEvents (this=0xd165e0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#23 0x00007f74505fdcde in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007f744fb54e62 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f744fb550b7 in QEventLoop::exec (this=0x7fffe4a1f0e0, flags=...) at kernel/qeventloop.cpp:204
#26 0x00007f744fb5a407 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#27 0x00000000004919f3 in main (argc=3, argv=<optimized out>) at /build/buildd/digikam-3.3.0/core/digikam/main/main.cpp:235

Possible duplicates by query: bug 239896.

Reported using DrKonqi
Comment 1 caulier.gilles 2014-01-10 22:00:42 UTC
Can you try if last digiKam 3.5.0 fix the problem  ?

Gilles Caulier
Comment 2 caulier.gilles 2014-05-16 07:30:20 UTC
digiKam 4.0.0 is out :

http://www.digikam.org/node/713

Please check if this entry still valid with this new version.

Thanks in advance

Gilles Caulier
Comment 3 Jekyll Wu 2014-05-27 00:43:38 UTC
*** Bug 335370 has been marked as a duplicate of this bug. ***
Comment 4 caulier.gilles 2014-08-07 06:47:41 UTC
We need a fresh feedback using last digiKam 4.2.0 release...

Gilles Caulier
Comment 5 caulier.gilles 2015-06-28 09:40:43 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 6 caulier.gilles 2015-08-20 06:52:45 UTC
digiKam 4.12.0 is out :

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

We need a fresh feedback using this release please...
Thanks in advance.

Gilles Caulier
Comment 7 caulier.gilles 2016-07-02 15:34:20 UTC
With 5.0.0, the crash is not reproducible anymore.

I close this file now. Don't hesitate to re-open if necessary.

Gilles Caulier