Summary: | Digikam crashes | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Laurent Charrière <lcharriere> |
Component: | Database-Files | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, marcel.wiesweg, tschenser |
Priority: | NOR | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.3.0 | |
Sentry Crash Report: |
Description
Laurent Charrière
2010-01-19 08:06:12 UTC
Laurent, the last step is not clear to me. Do you either: - quit picaseweb export dialog and choose another local digikam album in digikam album view or - quit the the process dialog and choose another picasa web album to export to? Jens I quit the Picasa web export dialog and choose another local digikam album in digikam album view. Note that it is not 100% reproducible, more like 50% of the time. I have also noticed crashes while exporting to Picasa just after I click "start transfer" (not sure of the exact label because I use the French locale). I'm not sure if it's the same bug happening at a different time, or another bug. The crash location is really so far away from any Picasa-related code... I wonder if the Picasa plugin is introducing some memory corruption? Laurent, is the backtrace always the same? I'm referring to the few lines just below "[KCrash handler]" in thread 1. digiKam 1.1. release will be done in few days. Please check if this entry still valid. Thanks in advance Gilles Caulier In reply to comment #3: I was able to reproduce the crash with the exact same backtrace under KCrash Handler for thread 1. In another instance I had a crash with a completely different backtrace. This happened while selecting pictures for export to Picasa. I assume it is a different bug. The start of the backtrace is Thread 7 (Thread 0xa55feb70 (LWP 22836)): [KCrash Handler] #6 QBasicAtomicInt::operator== (this=0xa6f7b48) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:64 #7 QImage::isDetached (this=0xa6f7b48) at image/qimage.cpp:5581 #8 0xb69c63f4 in qIsDetached<QImage> (this=0x8a50f88, m=1117680) at /usr/include/qt4/QtGui/qimage.h:326 #9 QCache<QString, QImage>::trim (this=0x8a50f88, m=1117680) at /usr/include/qt4/QtCore/qcache.h:207 #10 0xb69c654f in QCache<QString, QImage>::insert (this=0x8a50f88, akey=..., aobject=0xa71a7e0, acost=193040) at /usr/include/qt4/QtCore/qcache.h:187 #11 0xb69c3d9b in Digikam::LoadingCache::putThumbnail (this=0x8952c18, cacheKey=..., thumb=..., filePath=...) at /build/buildd-digikam_1.0.0-1-i386-kdhbp1/digikam-1.0.0/libs/threadimageio/loadingcache.cpp:199 #12 0xb69dd8d6 in Digikam::ThumbnailLoadingTask::execute (this=0xb506b70) at /build/buildd-digikam_1.0.0-1-i386-kdhbp1/digikam-1.0.0/libs/threadimageio/thumbnailtask.cpp:139 #13 0xb69b6dca in Digikam::LoadSaveThread::run (this=0xa8aec58) at /build/buildd-digikam_1.0.0-1-i386-kdhbp1/digikam-1.0.0/libs/threadimageio/loadsavethread.cpp:134 #14 0xb4df45e2 in QThreadPrivate::start (arg=0xa8aec58) at thread/qthread_unix.cpp:188 #15 0xb47ca585 in start_thread () from /lib/i686/cmov/libpthread.so.0 #16 0xb4bf12be in clone () from /lib/i686/cmov/libc.so.6 A completely different crash, again not related to the Picasa plugin, and again after working with the Picasa plugin. Looks like another hint at any memory corruption introduced by the Picasa plugin. I recommend too to use kipi-plugins 1.1.0 here. Gilles Caulier digiKam and Kipi-plugins 1.2.0 are out. Please check if crash is still valid there. Thanks in advance Gilles Caulier I am now using 1.1 and have not seen the crash. I have not upgraded to 1.2 yet because I use Debian and it's not even in unstable yet. If I was you I would close the bug for now, marking resolved as of 1.1. I will be sure to ask for it to be reopened it I see the problem again. |