[Digikam-devel] [Bug 274713] Digikam crashed unexpectedly

[Graham Watson]

https://bugs.kde.org/show_bug.cgi?id=274713


Graham Watson <grahamw.home at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|WAITINGFORINFO              |




--- Comment #2 from Graham Watson <grahamw home gmail com>  2011-06-08 21:29:49 ---
Hi,

I don't see how you can say that it isn't a digikam problem - it was clearly
the digikam exe that crashed, even if the actual assert is coming from one of
the support libraries. Sure it is thread 7 which asserted, but that thread
'belongs' to Digikam.

I'm a programmer myself (professional c++). I've not done much programming in
Linux, but from the backtrace it looks to me like something (not me) has caused
the application to exit, and thread 1 is in the process of exiting digikam and
in the middle of calling the ThreadManagerCreator destructor, which is waiting
inside a QThreadPool destructor for the threadpool thread to exit. The assert
appears to be from an unrelated thread (probably the QThreadPool thread) but I
would guess that it is busy with something that digikam is in the middle of
destroying or has just destroyed prior to destroying the QThreadPool. Is it
possible that you are cleaning up the data that the thread pool is using before
stopping the thread pool?

Reading it again - libavahi has called abort, which is perhaps the reason for
digikam to be shutting down, but perhaps my above hypothesis still stands - it
should shut down cleanly in all situations. It does look network related so
might be reproducible by the steps I described earlier. Perhaps an
interdependency between yanking the network cable whilst the threadpool is at
work and it not handling a clean shutdown?

Loving Digikam btw, if there's anything I can help with give me a shout :)

Regards
Graham

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.