Crash when closing digikam immediatly

Hi,

when I close digiKam right after startup (with thumbsDB enabled), it crashes.
This seems to happen as long as the album thumbnails are generated (which
takes some time since using the thumbsDB).

Here is the bt:
(gdb) bt
#0  0xb5743ee7 in QMutex::lock () from /usr/lib/libQtCore.so.4
#1  0xb7252ef8 in CacheLock (this=0xaa2cf290, cache=0x878c1c0) at
/home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimageio/loadingcache.cpp:445
#2  0xb7265a7d in Digikam::ThumbnailLoadingTask::execute (this=0xa7c2c868) at
/home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimageio/thumbnailtask.cpp:138
#3  0xb724d82f in Digikam::LoadSaveThread::run (this=0xadacb40) at
/home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimageio/loadsavethread.cpp:139
#4  0xb57492ce in ?? () from /usr/lib/libQtCore.so.4
#5  0xb56c26bc in start_thread () from /lib/libpthread.so.0
#6  0xb550cffe in clone () from /lib/libc.so.6
(gdb)


Andi

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Another crash... But I guess this is the same backtrace:

Thread [36] (Suspended: Signal 'SIGSEGV' received. Description: Segmentation
fault.)
        7 QMutex::lock()  0xb57e6ee7
        6 CacheLock()
/home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimageio/loadingcache.cpp:445
0xb72f8d98
        5 Digikam::ThumbnailLoadingTask::execute()
/home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimageio/thumbnailtask.cpp:138
0xb730bc0d
        4 Digikam::LoadSaveThread::run()
/home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimageio/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?

Andi

On Sunday 14 June 2009 18:09:01 Andi Clemens wrote:

> Hi,
>
> when I close digiKam right after startup (with thumbsDB enabled), it
> crashes. This seems to happen as long as the album thumbnails are generated
> (which takes some time since using the thumbsDB).
>
> Here is the bt:
> (gdb) bt
> #0  0xb5743ee7 in QMutex::lock () from /usr/lib/libQtCore.so.4
> #1  0xb7252ef8 in CacheLock (this=0xaa2cf290, cache=0x878c1c0) at
> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>o/loadingcache.cpp:445 #2  0xb7265a7d in
> Digikam::ThumbnailLoadingTask::execute (this=0xa7c2c868) at
> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>o/thumbnailtask.cpp:138 #3  0xb724d82f in Digikam::LoadSaveThread::run
> (this=0xadacb40) at
> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>o/loadsavethread.cpp:139 #4  0xb57492ce in ?? () from
> /usr/lib/libQtCore.so.4
> #5  0xb56c26bc in start_thread () from /lib/libpthread.so.0
> #6  0xb550cffe in clone () from /lib/libc.so.6
> (gdb)
>
>
> Andi
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

> 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.

Marcel
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Marcel,

I ran digiKam under valgrind now, maybe this helps?
I had to kill valgrind in the end because it just didn't stop to operate, so
maybe the backtrace is incomplete.

I'll attach it to this mail.

Andi

On Saturday 20 June 2009 12:16:54 Marcel Wiesweg wrote:

> > Thread [36] (Suspended: Signal 'SIGSEGV' received. Description:
> > Segmentation fault.)
> > 7 QMutex::lock()  0xb57e6ee7
> > 6 CacheLock()
> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimag
> >ei o/loadingcache.cpp:445 0xb72f8d98
> > 5 Digikam::ThumbnailLoadingTask::execute()
> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimag
> >ei o/thumbnailtask.cpp:138 0xb730bc0d
> > 4 Digikam::LoadSaveThread::run()
> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimag
> >ei 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.
>
> Marcel
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Stupid mailing list with its limitations!
Marcel, I will sent you the backtrace to your private mail address.

Andi

On Saturday 20 June 2009 12:16:54 Marcel Wiesweg wrote:

> > Thread [36] (Suspended: Signal 'SIGSEGV' received. Description:
> > Segmentation fault.)
> > 7 QMutex::lock()  0xb57e6ee7
> > 6 CacheLock()
> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimag
> >ei o/loadingcache.cpp:445 0xb72f8d98
> > 5 Digikam::ThumbnailLoadingTask::execute()
> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimag
> >ei o/thumbnailtask.cpp:138 0xb730bc0d
> > 4 Digikam::LoadSaveThread::run()
> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimag
> >ei 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.
>
> Marcel
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

2009/6/20 Andi Clemens <[hidden email]>:
> Stupid mailing list with its limitations!

hum, i think there is not size limitations for devel ML...

Gilles

> Marcel, I will sent you the backtrace to your private mail address.
>
> Andi
>
> On Saturday 20 June 2009 12:16:54 Marcel Wiesweg wrote:
>> > Thread [36] (Suspended: Signal 'SIGSEGV' received. Description:
>> > Segmentation fault.)
>> >     7 QMutex::lock()  0xb57e6ee7
>> >     6 CacheLock()
>> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimag
>> >ei o/loadingcache.cpp:445 0xb72f8d98
>> >     5 Digikam::ThumbnailLoadingTask::execute()
>> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimag
>> >ei o/thumbnailtask.cpp:138 0xb730bc0d
>> >     4 Digikam::LoadSaveThread::run()
>> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimag
>> >ei 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.
>>
>> Marcel
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

There is, 170k
On Saturday 20 June 2009 15:26:15 Gilles Caulier wrote:

> 2009/6/20 Andi Clemens <[hidden email]>:
> > Stupid mailing list with its limitations!
>
> hum, i think there is not size limitations for devel ML...
>
> Gilles
>
> > Marcel, I will sent you the backtrace to your private mail address.
> >
> > Andi
> >
> > On Saturday 20 June 2009 12:16:54 Marcel Wiesweg wrote:
> >> > Thread [36] (Suspended: Signal 'SIGSEGV' received. Description:
> >> > Segmentation fault.)
> >> >     7 QMutex::lock()  0xb57e6ee7
> >> >     6 CacheLock()
> >> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadi
> >> >mag ei o/loadingcache.cpp:445 0xb72f8d98
> >> >     5 Digikam::ThumbnailLoadingTask::execute()
> >> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadi
> >> >mag ei o/thumbnailtask.cpp:138 0xb730bc0d
> >> >     4 Digikam::LoadSaveThread::run()
> >> > /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadi
> >> >mag ei 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.
> >>
> >> Marcel
> >> _______________________________________________
> >> Digikam-devel mailing list
> >> [hidden email]
> >> https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-devel
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

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
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

To get the crash, you seem to need many albums, and, in the best case, have an
thumbnail set for every album.

It takes a while until the album folderview is filled and when you close
digiKam during this process, you can crash it. Everytime.

I will try to add a kdebug().

Andi

On Saturday 20 June 2009 17:14:53 Marcel Wiesweg wrote:

> 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
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Saturday 20 June 2009 18:06:02 Andi Clemens wrote:
> To get the crash, you seem to need many albums, and, in the best case, have
> an thumbnail set for every album.
>
> It takes a while until the album folderview is filled and when you close

filled with the thumbnails I meant...


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

I just installed digiKam 0.10.0 and it also crashes when you immediately close
digiKam after startup, so at least this is no thumbsDB issue.

I don't know how to track down this bug, all debug output is saying nothing
special.

Andi

On Sunday 14 June 2009 18:09:01 Andi Clemens wrote:

> Hi,
>
> when I close digiKam right after startup (with thumbsDB enabled), it
> crashes. This seems to happen as long as the album thumbnails are generated
> (which takes some time since using the thumbsDB).
>
> Here is the bt:
> (gdb) bt
> #0  0xb5743ee7 in QMutex::lock () from /usr/lib/libQtCore.so.4
> #1  0xb7252ef8 in CacheLock (this=0xaa2cf290, cache=0x878c1c0) at
> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>o/loadingcache.cpp:445 #2  0xb7265a7d in
> Digikam::ThumbnailLoadingTask::execute (this=0xa7c2c868) at
> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>o/thumbnailtask.cpp:138 #3  0xb724d82f in Digikam::LoadSaveThread::run
> (this=0xadacb40) at
> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>o/loadsavethread.cpp:139 #4  0xb57492ce in ?? () from
> /usr/lib/libQtCore.so.4
> #5  0xb56c26bc in start_thread () from /lib/libpthread.so.0
> #6  0xb550cffe in clone () from /lib/libc.so.6
> (gdb)
>
>
> Andi
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

and valgrind ?

Gilles

2009/6/28 Andi Clemens <[hidden email]>:

> I just installed digiKam 0.10.0 and it also crashes when you immediately close
> digiKam after startup, so at least this is no thumbsDB issue.
>
> I don't know how to track down this bug, all debug output is saying nothing
> special.
>
> Andi
>
> On Sunday 14 June 2009 18:09:01 Andi Clemens wrote:
>> Hi,
>>
>> when I close digiKam right after startup (with thumbsDB enabled), it
>> crashes. This seems to happen as long as the album thumbnails are generated
>> (which takes some time since using the thumbsDB).
>>
>> Here is the bt:
>> (gdb) bt
>> #0  0xb5743ee7 in QMutex::lock () from /usr/lib/libQtCore.so.4
>> #1  0xb7252ef8 in CacheLock (this=0xaa2cf290, cache=0x878c1c0) at
>> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>>o/loadingcache.cpp:445 #2  0xb7265a7d in
>> Digikam::ThumbnailLoadingTask::execute (this=0xa7c2c868) at
>> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>>o/thumbnailtask.cpp:138 #3  0xb724d82f in Digikam::LoadSaveThread::run
>> (this=0xadacb40) at
>> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadimagei
>>o/loadsavethread.cpp:139 #4  0xb57492ce in ?? () from
>> /usr/lib/libQtCore.so.4
>> #5  0xb56c26bc in start_thread () from /lib/libpthread.so.0
>> #6  0xb550cffe in clone () from /lib/libc.so.6
>> (gdb)
>>
>>
>> Andi
>>
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

I had posted this already to Marcel, and he suggested to add a kdebug in an
appropriate place. But this kdebug doesn't seem to output useful information.

It is a race condition when deleting the thumbnailing threads, at least it
looks like that.

You can "visually" see this: while the album thumbnails on the left  are
generated, digiKam will crash when closing it. When they all are created, it
quits normally.

Andi

On Sunday 28 June 2009 10:17:33 Gilles Caulier wrote:

> and valgrind ?
>
> Gilles
>
> 2009/6/28 Andi Clemens <[hidden email]>:
> > I just installed digiKam 0.10.0 and it also crashes when you immediately
> > close digiKam after startup, so at least this is no thumbsDB issue.
> >
> > I don't know how to track down this bug, all debug output is saying
> > nothing special.
> >
> > Andi
> >
> > On Sunday 14 June 2009 18:09:01 Andi Clemens wrote:
> >> Hi,
> >>
> >> when I close digiKam right after startup (with thumbsDB enabled), it
> >> crashes. This seems to happen as long as the album thumbnails are
> >> generated (which takes some time since using the thumbsDB).
> >>
> >> Here is the bt:
> >> (gdb) bt
> >> #0  0xb5743ee7 in QMutex::lock () from /usr/lib/libQtCore.so.4
> >> #1  0xb7252ef8 in CacheLock (this=0xaa2cf290, cache=0x878c1c0) at
> >> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadima
> >>gei o/loadingcache.cpp:445 #2  0xb7265a7d in
> >> Digikam::ThumbnailLoadingTask::execute (this=0xa7c2c868) at
> >> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadima
> >>gei o/thumbnailtask.cpp:138 #3  0xb724d82f in
> >> Digikam::LoadSaveThread::run (this=0xadacb40) at
> >> /home/andi/Programmieren/KDE/digiKam/digikam_KDE4/digikam/libs/threadima
> >>gei o/loadsavethread.cpp:139 #4  0xb57492ce in ?? () from
> >> /usr/lib/libQtCore.so.4
> >> #5  0xb56c26bc in start_thread () from /lib/libpthread.so.0
> >> #6  0xb550cffe in clone () from /lib/libc.so.6
> >> (gdb)
> >>
> >>
> >> Andi
> >>
> >> _______________________________________________
> >> Digikam-devel mailing list
> >> [hidden email]
> >> https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-devel
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

> I had posted this already to Marcel, and he suggested to add a kdebug in an
> appropriate place. But this kdebug doesn't seem to output useful
> information.

I just saw that the AlbumThumbnailLoader has its own thread objects created.
These need to be deleted of course at shutdown. I will add a cleanUp method.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel