[Digikam-devel] Crash when closing digikam immediatly

Marcel Wiesweg marcel.wiesweg at gmx.de
Sat Jun 20 11:16:54 BST 2009

> Thread [36] (Suspended: Signal 'SIGSEGV' received. Description:
> Segmentation fault.)
> 	7 QMutex::lock()  0xb57e6ee7
> 	6 CacheLock()
> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>o/loadingcache.cpp:445 0xb72f8d98
> 	5 Digikam::ThumbnailLoadingTask::execute()
> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>o/thumbnailtask.cpp:138 0xb730bc0d
> 	4 Digikam::LoadSaveThread::run()
> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>o/loadsavethread.cpp:139 0xb72f36cf
> 	3 <symbol is not available> 0xb57ec2ce
> 	2 start_thread()  0xb578b6bc
> 	1 clone()  0xb55d6ffe
> Oh yeah it is :D
> I just copied it and have not looked into the mail...
> Well anyway what can be the reason for the crash? Shouldn't DB connections
> get closed when I close digiKam?

It seems that one thread is still running when the LoadingCache has been 
destroyed. That surely must crash.
Can you identify which thread it is?
~DigikamApp() call ThumbnailLoadThread::cleanUp() which destroys the three 
global default threads. Is it one of them? Anything going wrong here?
~ThumbnailLoadThread() calls shutDownThread() which deletes all tasks and 
waits for the thread to finish.


More information about the Digikam-devel mailing list