| Summary: | digiKam crashes on startup while scanning image metadata | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Sami Nieminen <sami.nieminen> |
| Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | ahuggel, andresbajotierra, caulier.gilles |
| Priority: | NOR | ||
| Version: | 1.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.3.0 | |
| Sentry Crash Report: | |||
|
Description
Sami Nieminen
2010-01-01 11:10:40 UTC
Sound like the problem is in Exiv2 library. Which version you use ? Gilles Caulier libexiv2-5 0.18.2-1 Ok, try with 0.19.0 out few ago. note : libkexiv2 from KDE core used by digiKam and kipi-plugins must be recompiled because binary compatibility is broken. Look in Help/Components Info from digiKam or Showfoto for details. Gilles Caulier Gilles, The crash is not in libexiv2. It's in this part: Thread 1 (Thread 0xb789c790 (LWP 7563)): [KCrash Handler] #6 0x008d7422 in __kernel_vsyscall () #7 0x02e664d1 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0x02e69932 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0x02e9cee5 in ?? () from /lib/tls/i686/cmov/libc.so.6 #10 0x02ea6ff1 in ?? () from /lib/tls/i686/cmov/libc.so.6 #11 0x02eab806 in free () from /lib/tls/i686/cmov/libc.so.6 #12 0x015900fb in QRegion::cleanUp (x=0x0) at painting/qregion.cpp:3924 #13 0x015901bb in ~QRegion (this=0x6, __in_chrg=<value optimized out>) at painting/qregion.cpp:3935 Andreas Andreas, If crash is there, well, why. It's process which draw progress in splashscreen during startup. Thereis nothing special here. or perhaps a Qt bug. Sami, which QT4 version you use exactly ? Gilles Caulier Sami, Look if it's not the same KDE core issue : https://bugs.kde.org/show_bug.cgi?id=220708#c1 Gilles Caulier My qt version is 4.6.0.
It seems indeed that the crash is not related to libexiv2 at all. When I reproduce the crash backtrace, it is almost every time little different, but always having to do with some free() call, like here:
Thread 13 (Thread 0xb48dcb70 (LWP 8711)):
[KCrash Handler]
#6 0x006d8422 in __kernel_vsyscall ()
#7 0x02b604d1 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0x02b63932 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0x02b96ee5 in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0x02ba0ff1 in ?? () from /lib/tls/i686/cmov/libc.so.6
#11 0x02ba5806 in free () from /lib/tls/i686/cmov/libc.so.6
#12 0x00cdd6f1 in operator delete(void*) () from /usr/lib/libstdc++.so.6
#13 0x00cdd74d in operator delete[](void*) () from /usr/lib/libstdc++.so.6
#14 0x0770c239 in CSubband::FreeMemory (this=0x0) at /build/buildd/digikam-1.0.0/libs/3rdparty/libpgf/Subband.cpp:96
#15 0x0770cfa0 in CWaveletTransform::InverseTransform (this=0xb0614d0, srcLevel=2, w=0xb48db98c, h=0xb48db9ac, data=0xb48db964)
at /build/buildd/digikam-1.0.0/libs/3rdparty/libpgf/WaveletTransform.cpp:353
#16 0x0770a66a in CPGFImage::Read (this=0xb48db940, level=0, cb=0, data=0x0) at /build/buildd/digikam-1.0.0/libs/3rdparty/libpgf/PGFimage.cpp:299
#17 0x0770e756 in Digikam::readPGFImageData (data=..., img=...) at /build/buildd/digikam-1.0.0/libs/threadimageio/pgfutils.cpp:68
#18 0x076e7662 in Digikam::ThumbnailCreator::loadFromDatabase (this=0x969cd10, info=...) at /build/buildd/digikam-1.0.0/libs/threadimageio/thumbnailcreator.cpp:587
It can be the same issue like the #220708 report is talking about. When I set:
export QT_NO_GLIB=1
export MALLOC_CHECK_=
and then start digikam from console, I couldn't reproduce the crash anymore. Also sometimes I can start digikam without that trick, but it crashes after some time later.
Then, this is the same crash as bug 196207 (a glibc bug). Merging. Thanks *** This bug has been marked as a duplicate of bug 196207 *** Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4 |