Summary: | digikam crashed when browsing/rating images | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Oldřich Jedlička <oldium.pro> |
Component: | Preview-Image | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | basosergiou, caulier.gilles, jens, psummitt, renda.krell, trast |
Priority: | NOR | ||
Version: | 1.5.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.8.0 | |
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Oldřich Jedlička
2010-11-02 07:07:51 UTC
Important is Thread 2, which indicates a call to pure virtual function. I had simillar problem in my application and the cause is usage of already freed or freeing instance - when the destructor of implementing class is called, its virtual table gets reset. yes, in preview manager. Marcel ? Gilles Caulier I have seen similar crash in the branch when using a preview thread in the really heavily multithreaded environment of the FacePipeline. It is probably fixed in branch. The question is if we should backport dynamicthread.cpp from branch to trunk. Pro: In branch, it has been put under much heavier load, bugs were discovered and fixed. Con: It contains some new code parts that did not receive a lot of testing. I'm pro to backport. As trunk is used more than branch, it will be tested faster. Gilles Caulier 2010/11/2 Marcel Wiesweg <marcel.wiesweg@gmx.de>: > https://bugs.kde.org/show_bug.cgi?id=255852 > > > > > > --- Comment #3 from Marcel Wiesweg <marcel wiesweg gmx de> 2010-11-02 10:17:55 --- > I have seen similar crash in the branch when using a preview thread in the > really heavily multithreaded environment of the FacePipeline. It is probably > fixed in branch. > > The question is if we should backport dynamicthread.cpp from branch to trunk. > Pro: In branch, it has been put under much heavier load, bugs were discovered > and fixed. Con: It contains some new code parts that did not receive a lot of > testing. > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are the assignee for the bug. > _______________________________________________ > Digikam-devel mailing list > Digikam-devel@kde.org > https://mail.kde.org/mailman/listinfo/digikam-devel > Created attachment 53147 [details]
New crash information added by DrKonqi
digikam (1.5.0) on KDE Platform 4.5.3 (KDE 4.5.3) "release 8" using Qt 4.6.3
Had a crash with apparently the same backtrace while deleting images.
This is behaviourally very similar to the bug I reported back in August(?): deleting images and navigating between them at a rather fast rate apparently confuses digikam.
-- Backtrace (Reduced):
#8 0x00007fd71df3bcdd in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93
#9 0x00007fd71df39ef6 in __cxxabiv1::__terminate (handler=<value optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:39
#10 0x00007fd71df39f23 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:49
#11 0x00007fd71df3a87f in __cxxabiv1::__cxa_pure_virtual () at ../../../../libstdc++-v3/libsupc++/pure.cc:50
#12 0x00007fd7212e33a1 in Digikam::LoadingCache::addLoadingProcess (this=0xe44af0, process=0x7fd6e9a9fdd0) at /usr/src/debug/digikam-1.5.0/libs/threadimageio/loadingcache.cpp:151
It's the same trace than this file : https://bugs.kde.org/show_bug.cgi?id=253728 Gilles Caulier *** Bug 256481 has been marked as a duplicate of this bug. *** SVN commit 1195034 by mwiesweg: Backport thread classes from branch CCBUG: 255852 M +52 -8 dynamicthread.cpp M +14 -0 dynamicthread.h M +26 -7 threadmanager.cpp M +68 -19 workerobject.cpp M +56 -8 workerobject.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1195034 digiKam 1.6.0 is out: http://www.digikam.org/drupal/node/550 Please update and check if this entry still valid. Thanks in advance Gilles Caulier *** Bug 261664 has been marked as a duplicate of this bug. *** digiKam 1.7.0 is out. This bug is probably fixed (in fact i never reproduce it here). Please update and try again, else i will close this file as well... Gilles Caulier Looks like fixed, I didn't see the crash for some time now. *** Bug 255256 has been marked as a duplicate of this bug. *** *** Bug 255953 has been marked as a duplicate of this bug. *** |