Summary: | digikam crashes while importing images (about 60000 files) | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Stefan Holmström <stefan.ca.h> |
Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | ahuggel, caulier.gilles, sam.chola+kdebugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.7.0 | |
Sentry Crash Report: |
Description
Stefan Holmström
2010-04-01 13:49:14 UTC
First you use digiKam 1.0.0-beta5. It's not maintained. update to digiKam 1.2.0. Second, crash sound like located to Exiv2 library, not digiKam... Gilles Caulier Standard question for exiv2 issues is: Can you reproduce this with the exiv2 command line tool? If so, please provide the image that triggers the problem. (The crash actually happens in a function called _wordcopy_fwd_aligned, which is not part of libexiv2. After scanning roughly 40,000 images...) Thanks, Andreas Hello Andreas and also Gilles Caulier Thank you for the quick response. This bug is most probably related to the old release of DigiKam that is the default in Ubuntu. After upgrading to 1.1.0 the crash did not reappear. So from my point of view, the bug is resolved. Regards Stefan Andreas Huggel skrev 2010-04-01 15:34: > https://bugs.kde.org/show_bug.cgi?id=232957 > > > Andreas Huggel<ahuggel@gmx.net> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |ahuggel@gmx.net > > > > > --- Comment #2 from Andreas Huggel<ahuggel gmx net> 2010-04-01 15:33:48 --- > Standard question for exiv2 issues is: Can you reproduce this with the exiv2 > command line tool? If so, please provide the image that triggers the problem. > > (The crash actually happens in a function called _wordcopy_fwd_aligned, which > is not part of libexiv2. After scanning roughly 40,000 images...) > > Thanks, > Andreas > > I am also affected by this bug. My photo library is fairly large (approx. 100GB) and digikam has been crashing every time on startup. It seems to be related to exiv2. Here is the trace. Symbols were not available for exiv2 so I could not use the automated crash reporter. I am running Ububtu 10.04 x86 on an HP Pavillion dv4-1413la with an Athlon X2 processor. Application: digikam (1.2.0) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-22-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Crashes on startup every time. The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Bus error [Current thread is 1 (Thread 0xb66be760 (LWP 13941))] Thread 2 (Thread 0xb4f0db70 (LWP 13942)): [KCrash Handler] #6 0x07d22915 in ?? () from /lib/tls/i686/cmov/libc.so.6 #7 0x014a87d1 in void std::vector<unsigned char, std::allocator<unsigned char> >::_M_assign_aux<unsigned char const*>(unsigned char const*, unsigned char const*, std::forward_iterator_tag) () from /usr/lib/libexiv2.so.6 #8 0x014a3bc5 in Exiv2::DataValue::read(unsigned char const*, long, Exiv2::ByteOrder) () from /usr/lib/libexiv2.so.6 #9 0x0149d94e in ?? () from /usr/lib/libexiv2.so.6 #10 0x0149e53e in ?? () from /usr/lib/libexiv2.so.6 #11 0x0148b64c in ?? () from /usr/lib/libexiv2.so.6 #12 0x0148b4b0 in ?? () from /usr/lib/libexiv2.so.6 #13 0x0148b76d in ?? () from /usr/lib/libexiv2.so.6 #14 0x0148b4b0 in ?? () from /usr/lib/libexiv2.so.6 #15 0x0148b709 in ?? () from /usr/lib/libexiv2.so.6 #16 0x0148b4b0 in ?? () from /usr/lib/libexiv2.so.6 #17 0x0148b76d in ?? () from /usr/lib/libexiv2.so.6 #18 0x0148b4b0 in ?? () from /usr/lib/libexiv2.so.6 #19 0x01492d7e in ?? () from /usr/lib/libexiv2.so.6 #20 0x014936ba in ?? () from /usr/lib/libexiv2.so.6 #21 0x0140a8e2 in Exiv2::Cr2Parser::decode(Exiv2::ExifData&, Exiv2::IptcData&, Exiv2::XmpData&, unsigned char const*, unsigned int) () from /usr/lib/libexiv2.so.6 #22 0x0140bb24 in Exiv2::Cr2Image::readMetadata() () from /usr/lib/libexiv2.so.6 #23 0x0014c6d5 in KExiv2Iface::KExiv2::load(QString const&) const () from /usr/lib/libkexiv2.so.8 #24 0x07040b8c in Digikam::DMetadata::load (this=0xb4f0ccfc, filePath=...) at /build/buildd/digikam-1.2.0/libs/dmetadata/dmetadata.cpp:78 #25 0x011dfd8a in Digikam::ImageScanner::loadFromDisk (this=0xb4f0ccf4) at /build/buildd/digikam-1.2.0/libs/database/imagescanner.cpp:592 #26 0x011e5892 in Digikam::ImageScanner::newFile (this=0xb4f0ccf4, albumId=174) at /build/buildd/digikam-1.2.0/libs/database/imagescanner.cpp:98 #27 0x01191e24 in Digikam::CollectionScanner::scanNewFile (this=0xb4f0d290, info=..., albumId=174) at /build/buildd/digikam-1.2.0/libs/database/collectionscanner.cpp:756 #28 0x01192bfa in Digikam::CollectionScanner::scanAlbum (this=0xb4f0d290, location=..., album=...) at /build/buildd/digikam-1.2.0/libs/database/collectionscanner.cpp:665 #29 0x01192a7c in Digikam::CollectionScanner::scanAlbum (this=0xb4f0d290, location=..., album=...) at /build/buildd/digikam-1.2.0/libs/database/collectionscanner.cpp:683 #30 0x01192a7c in Digikam::CollectionScanner::scanAlbum (this=0xb4f0d290, location=..., album=...) at /build/buildd/digikam-1.2.0/libs/database/collectionscanner.cpp:683 #31 0x01192a7c in Digikam::CollectionScanner::scanAlbum (this=0xb4f0d290, location=..., album=...) at /build/buildd/digikam-1.2.0/libs/database/collectionscanner.cpp:683 #32 0x01193897 in Digikam::CollectionScanner::scanAlbumRoot (this=0xb4f0d290, location=...) at /build/buildd/digikam-1.2.0/libs/database/collectionscanner.cpp:479 #33 0x01193bcf in Digikam::CollectionScanner::completeScan (this=0xb4f0d290) at /build/buildd/digikam-1.2.0/libs/database/collectionscanner.cpp:250 #34 0x08321f6e in Digikam::ScanController::run (this=0x9d1f6a0) at /build/buildd/digikam-1.2.0/digikam/scancontroller.cpp:541 #35 0x01de632e in QThreadPrivate::start (arg=0x9d1f6a0) at thread/qthread_unix.cpp:248 #36 0x0096c96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #37 0x07d7ba4e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb66be760 (LWP 13941)): #0 0x00291422 in __kernel_vsyscall () #1 0x00971015 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x01de7287 in QWaitConditionPrivate::wait (this=0x9d29bf4, mutex=0x9d29be0, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #3 QWaitCondition::wait (this=0x9d29bf4, mutex=0x9d29be0, time=4294967295) at thread/qwaitcondition_unix.cpp:159 #4 0x01de63c9 in QThread::wait (this=0x9d1f6a0, time=4294967295) at thread/qthread_unix.cpp:619 #5 0x08322354 in Digikam::ScanController::shutDown (this=0x9d1f6a0) at /build/buildd/digikam-1.2.0/digikam/scancontroller.cpp:290 #6 0x08323ab1 in ~ScanController (this=0x9d1f6a0, __in_chrg=<value optimized out>) at /build/buildd/digikam-1.2.0/digikam/scancontroller.cpp:273 #7 0x08323c6a in ~ScanControllerCreator () at /build/buildd/digikam-1.2.0/digikam/scancontroller.cpp:221 #8 destroy () at /build/buildd/digikam-1.2.0/digikam/scancontroller.cpp:222 #9 0x07cdd1bf in ?? () from /lib/tls/i686/cmov/libc.so.6 #10 0x07cdd22f in exit () from /lib/tls/i686/cmov/libc.so.6 #11 0x097f2520 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #12 0x078b9bfa in KApplication::xioErrhandler (this=0xbfbfeac8, dpy=0x9bd45c8) at ../../kdeui/kernel/kapplication.cpp:408 #13 0x078b9c36 in kde_xio_errhandler (dpy=0x9bd45c8) at ../../kdeui/kernel/kapplication.cpp:125 #14 0x0322dc16 in _XIOError () from /usr/lib/libX11.so.6 #15 0x03235a1a in ?? () from /usr/lib/libX11.so.6 #16 0x03236356 in _XEventsQueued () from /usr/lib/libX11.so.6 #17 0x0321eadf in XEventsQueued () from /usr/lib/libX11.so.6 #18 0x05046305 in x11EventSourceCheck (s=0x9bbd140) at kernel/qguieventdispatcher_glib.cpp:87 #19 0x09547799 in g_main_context_check () from /lib/libglib-2.0.so.0 #20 0x095480ce in ?? () from /lib/libglib-2.0.so.0 #21 0x095484b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #22 0x01f145d5 in QEventDispatcherGlib::processEvents (this=0x9b8f6e8, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #23 0x05046135 in QGuiEventDispatcherGlib::processEvents (this=0x9b8f6e8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #24 0x01ee7059 in QEventLoop::processEvents (this=0x9d20e48, flags=) at kernel/qeventloop.cpp:149 #25 0x01ee74aa in QEventLoop::exec (this=0x9d20e48, flags=...) at kernel/qeventloop.cpp:201 #26 0x0832331c in Digikam::ScanController::completeCollectionScan (this=0x9d1f6a0, splash=0x9d4e710) at /build/buildd/digikam-1.2.0/digikam/scancontroller.cpp:378 #27 0x082cee72 in DigikamApp (this=0x9d94d40, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /build/buildd/digikam-1.2.0/digikam/digikamapp.cpp:189 #28 0x083c292a in main (argc=5, argv=0xbfbfef14) at /build/buildd/digikam-1.2.0/digikam/main.cpp:170 Sam, update Exiv2 library to 0.20, recompile (or update) libkexiv2 and try again Gilles Caulier This is a crash in Exiv2 library. digiKam 5.7.0 we use last Exiv2 0.26 where this crash must not reappear. |