[Digikam-devel] Crash when closing digikam immediatly

Marcel Wiesweg marcel.wiesweg at gmx.de
Sat Jun 20 17:14:53 CEST 2009


Am Samstag, 20. Juni 2009 schrieb Andi Clemens:
> Stupid mailing list with its limitations!
> Marcel, I will sent you the backtrace to your private mail address.
>
> Andi
>

The first error is enough info:
==1425== Thread 16:
==1425== Invalid read of size 4
==1425==    at 0x4D4BD8A: 
Digikam::LoadingCache::CacheLock::CacheLock(Digikam::LoadingCache*) 
(loadingcache.cpp:445)
==1425==    by 0x4D5EC0C: Digikam::ThumbnailLoadingTask::execute() 
(thumbnailtask.cpp:138)
==1425==    by 0x4D466CE: Digikam::LoadSaveThread::run() 
(loadsavethread.cpp:139)
==1425==    by 0x67092CD: (within /usr/lib/libQtCore.so.4.5.1)
==1425==    by 0x69186BB: start_thread (in /lib/libpthread-2.10.1.so)
==1425==    by 0x6B2FFFD: clone (in /lib/libc-2.10.1.so)
==1425==  Address 0xa735310 is 8 bytes inside a block of size 12 free'd
==1425==    at 0x4023A5A: operator delete(void*) (in /usr/lib/valgrind/x86-
linux/vgpreload_memcheck.so)
==1425==    by 0x4D4D3F8: Digikam::LoadingCache::~LoadingCache() 
(loadingcache.cpp:104)
==1425==    by 0x4D4BC15: Digikam::LoadingCache::cleanUp() 
(loadingcache.cpp:85)
==1425==    by 0x4D53076: Digikam::LoadingCacheInterface::cleanUp() 
(loadingcacheinterface.cpp:40)
==1425==    by 0x8236C1D: Digikam::DigikamApp::~DigikamApp() 
(digikamapp.cpp:284)

~DigikamApp has been run, CacheLock is deleted, and the three default 
ThumbnailLoadThread should have been deleted already. The question is: which 
thread is Thread 16? Where is it created? You could add kDebug()<<this to 
constructor and destructor of ThumbnailLoadThread and check when they are 
deleted.
Unfortunately, I dont get the crash currently.

Marcel


More information about the Digikam-devel mailing list