Bug 300795 - Crashed when adding name on 50 photos
Summary: Crashed when adding name on 50 photos
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 2.6.0
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-29 06:06 UTC by jm.bourgit
Modified: 2017-07-26 16:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jm.bourgit 2012-05-29 06:06:02 UTC
Application: digikam (2.5.0)
KDE Platform Version: 4.8.2 (4.8.2) (Compiled from sources)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed: after searching for faces, I was adding the name of the sun on more then 50 pictures

- Unusual behavior I noticed: the soft asked me to confirm the modification, when in the past it did not for the same exercise for the name of my wife (but less picture to modify)

-- 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 0x7fb4c6f36a00 (LWP 26532))]

Thread 6 (Thread 0x7fb4a701b700 (LWP 26535)):
#0  0x00007fb4c03bf0bd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007fb4b996c88f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fb4b9931abd in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fb4b9931f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fb4b993245a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fb4a702098b in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
#6  0x00007fb4b99539a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007fb4bbce4e9a in start_thread (arg=0x7fb4a701b700) at pthread_create.c:308
#8  0x00007fb4c03cc4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#9  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7fb4a681a700 (LWP 26536)):
#0  0x00007fb4b9903930 in pthread_mutex_lock@plt () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fb4b996d561 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fb4b9931824 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fb4b9931f6a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fb4b993245a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fb4af70c2c6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x00007fb4b99539a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007fb4bbce4e9a in start_thread (arg=0x7fb4a681a700) at pthread_create.c:308
#8  0x00007fb4c03cc4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#9  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7fb494ea6700 (LWP 26538)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fb4c11a04db in wait (time=18446744073709551615, this=0x185c820) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x185c718, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00000000005ca1d0 in Digikam::ScanController::run (this=0x185c4b0) at /build/buildd/digikam-2.5.0/core/digikam/database/scancontroller.cpp:647
#4  0x00007fb4c119ffcb in QThreadPrivate::start (arg=0x185c4b0) at thread/qthread_unix.cpp:298
#5  0x00007fb4bbce4e9a in start_thread (arg=0x7fb494ea6700) at pthread_create.c:308
#6  0x00007fb4c03cc4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7fb48ffff700 (LWP 26539)):
#0  __pthread_mutex_unlock_usercnt (mutex=<optimized out>, decr=<optimized out>) at pthread_mutex_unlock.c:66
#1  __pthread_mutex_unlock (mutex=0x7fb488000a60) at pthread_mutex_unlock.c:290
#2  0x00007fb4b996d591 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fb4b993189b in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fb4b9931f6a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fb4b9932124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007fb4c12ce426 in QEventDispatcherGlib::processEvents (this=0x7fb4880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#7  0x00007fb4c129dc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#8  0x00007fb4c129ded7 in QEventLoop::exec (this=0x7fb48fffeb50, flags=...) at kernel/qeventloop.cpp:204
#9  0x00007fb4c119cfa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#10 0x00007fb4c127d9ff in QInotifyFileSystemWatcherEngine::run (this=0x185eff0) at io/qfilesystemwatcher_inotify.cpp:248
#11 0x00007fb4c119ffcb in QThreadPrivate::start (arg=0x185eff0) at thread/qthread_unix.cpp:298
#12 0x00007fb4bbce4e9a in start_thread (arg=0x7fb48ffff700) at pthread_create.c:308
#13 0x00007fb4c03cc4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#14 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fb48f7fe700 (LWP 26541)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fb4c11a04db in wait (time=18446744073709551615, this=0x1bdcf00) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x1bdcc68, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00007fb4c459dff1 in Digikam::ParkingThread::run (this=0x1bdcc50) at /build/buildd/digikam-2.5.0/core/libs/threads/threadmanager.cpp:119
#4  0x00007fb4c119ffcb in QThreadPrivate::start (arg=0x1bdcc50) at thread/qthread_unix.cpp:298
#5  0x00007fb4bbce4e9a in start_thread (arg=0x7fb48f7fe700) at pthread_create.c:308
#6  0x00007fb4c03cc4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fb4c6f36a00 (LWP 26532)):
[KCrash Handler]
#6  deref (this=0x6100720072) at /usr/include/qt4/QtCore/qatomic_x86_64.h:133
#7  operator= (l=..., this=0x262aaf0) at /usr/include/qt4/QtCore/qlist.h:442
#8  Digikam::ImageInfo::tagIds (this=0x3eb1328) at /build/buildd/digikam-2.5.0/core/libs/database/imageinfo.cpp:559
#9  0x00007fb4c3f0d57c in Digikam::ImageInfo::colorLabel (this=0x3eb1328) at /build/buildd/digikam-2.5.0/core/libs/database/imageinfo.cpp:461
#10 0x000000000060ec15 in Digikam::MetadataHub::load (this=0x25e2ad8, info=...) at /build/buildd/digikam-2.5.0/core/digikam/metadata/metadatahub.cpp:184
#11 0x00000000004ae244 in Digikam::ImageDescEditTab::setInfos (this=0x25e2540, infos=...) at /build/buildd/digikam-2.5.0/core/libs/imageproperties/imagedescedittab.cpp:734
#12 0x00000000004ae9a2 in Digikam::ImageDescEditTab::setItem (this=0x25e2540, info=...) at /build/buildd/digikam-2.5.0/core/libs/imageproperties/imagedescedittab.cpp:698
#13 0x00000000004a06bb in Digikam::ImagePropertiesSideBarDB::slotChangedTab (this=0x24bc930, tab=0x25e2540) at /build/buildd/digikam-2.5.0/core/libs/imageproperties/imagepropertiessidebardb.cpp:294
#14 0x000000000049ddaa in Digikam::ImagePropertiesSideBarDB::itemChanged (this=0x24bc930, infos=..., rect=..., img=<optimized out>, history=...) at /build/buildd/digikam-2.5.0/core/libs/imageproperties/imagepropertiessidebardb.cpp:195
#15 0x000000000049f73b in Digikam::ImagePropertiesSideBarDB::itemChanged (this=0x24bc930, infos=...) at /build/buildd/digikam-2.5.0/core/libs/imageproperties/imagepropertiessidebardb.cpp:171
#16 0x000000000064d5d7 in Digikam::DigikamView::slotDispatchImageSelected (this=0x1bc2f30) at /build/buildd/digikam-2.5.0/core/digikam/views/digikamview.cpp:1185
#17 0x00007fb4c12b3281 in QMetaObject::activate (sender=0x28d0fb0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#18 0x00007fb4c12b8179 in QObject::event (this=0x28d0fb0, e=<optimized out>) at kernel/qobject.cpp:1157
#19 0x00007fb4c1c93894 in notify_helper (e=0x7fff7c1dd640, receiver=0x28d0fb0, this=0x163d4d0) at kernel/qapplication.cpp:4559
#20 QApplicationPrivate::notify_helper (this=0x163d4d0, receiver=0x28d0fb0, e=0x7fff7c1dd640) at kernel/qapplication.cpp:4531
#21 0x00007fb4c1c98713 in QApplication::notify (this=0x7fff7c1dda20, receiver=0x28d0fb0, e=0x7fff7c1dd640) at kernel/qapplication.cpp:4420
#22 0x00007fb4c29ccb46 in KApplication::notify (this=0x7fff7c1dda20, receiver=0x28d0fb0, event=0x7fff7c1dd640) at ../../kdeui/kernel/kapplication.cpp:311
#23 0x00007fb4c129ee9c in QCoreApplication::notifyInternal (this=0x7fff7c1dda20, receiver=0x28d0fb0, event=0x7fff7c1dd640) at kernel/qcoreapplication.cpp:876
#24 0x00007fb4c12d01f2 in sendEvent (event=0x7fff7c1dd640, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#25 QTimerInfoList::activateTimers (this=0x163cc60) at kernel/qeventdispatcher_unix.cpp:611
#26 0x00007fb4c12cdc0d in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#27 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#28 0x00007fb4b9931c9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007fb4b9932060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007fb4b9932124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007fb4c12ce3bf in QEventDispatcherGlib::processEvents (this=0x15dbb60, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#32 0x00007fb4c1d3bd5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x00007fb4c129dc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#34 0x00007fb4c129ded7 in QEventLoop::exec (this=0x7fff7c1dd8a0, flags=...) at kernel/qeventloop.cpp:204
#35 0x00007fb4c12a2f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#36 0x000000000048bc5d in main (argc=5, argv=<optimized out>) at /build/buildd/digikam-2.5.0/core/digikam/main/main.cpp:232

Reported using DrKonqi
Comment 1 caulier.gilles 2012-05-29 07:43:18 UTC
Crash probably fixed in 2.6.0... Can you test with Release Candidate please ?

Gilles Caulier
Comment 2 jm.bourgit 2012-05-29 20:14:05 UTC
hello team,
Soory I'm not a top gub in IT.
Hiw to install the 2.6.0. CR to dothe test ?
Jean-Michel
Comment 3 jm.bourgit 2012-05-29 20:19:52 UTC
Hello Gilles,
Thanks for the answer.
Can you please explain how to install 2.6.0.RC ?
i've downloaded the packagefrom froge, but don't know the next steps for 
the indtall .
Bgds,
Jean Michel

Le 29/05/2012 09:43, Gilles Caulier a écrit :
> https://bugs.kde.org/show_bug.cgi?id=300795
>
> Gilles Caulier<caulier.gilles@gmail.com>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |caulier.gilles@gmail.com
>            Component|general                     |Database
>
> --- Comment #1 from Gilles Caulier<caulier.gilles@gmail.com>  ---
> Crash probably fixed in 2.6.0... Can you test with Release Candidate please ?
>
> Gilles Caulier
>
Comment 4 caulier.gilles 2012-06-22 08:53:13 UTC
Official digiKam 2.6.0 release is out since few days now :

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

Please, check if this entry still valid, or update report accordingly.

Thanks in advance.

Gilles Caulier
Comment 5 jm.bourgit 2012-06-23 05:51:26 UTC
Hello Gilles,
This hapened to me with the version 2.6
Jean michel

Le 22/06/2012 10:53, Gilles Caulier a écrit :
> https://bugs.kde.org/show_bug.cgi?id=300795
>
> --- Comment #4 from Gilles Caulier<caulier.gilles@gmail.com>  ---
> Official digiKam 2.6.0 release is out since few days now :
>
> http://www.digikam.org/drupal/node/656
>
> Please, check if this entry still valid, or update report accordingly.
>
> Thanks in advance.
>
> Gilles Caulier
>
Comment 6 Marcel Wiesweg 2012-06-24 12:58:52 UTC
Can you provide the backtrace with 2.6.0 then? Above bt comes from 2.5, and the code has changed. Thanks.
Comment 7 Marcel Wiesweg 2012-10-03 14:22:23 UTC
see comment 6
Comment 8 caulier.gilles 2015-06-27 13:45:55 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 9 jm.bourgit 2015-06-28 06:19:25 UTC
The function looks relly instable.
As soon as I start to play with it, I encountered 2 crashes.
No need to ask to re name > 50 photos, even with few already crash.
JM

Le 27/06/2015 15:45, Gilles Caulier a écrit :
> https://bugs.kde.org/show_bug.cgi?id=300795
>
> --- Comment #8 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 10 caulier.gilles 2015-06-28 09:43:06 UTC
Are you have tested with 4.11.0 ?

The backtrace sound the same than before ?

Gilles Caulier
Comment 11 caulier.gilles 2015-08-21 07:05:31 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.
Comment 12 caulier.gilles 2016-07-02 15:33:17 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