Summary: | digikam crashes while creating thumbnails | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Salvatore Brigaglia <opensourcecat> |
Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | ahuggel, caulier.gilles, marcel.wiesweg |
Priority: | NOR | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.0.0 | |
Sentry Crash Report: |
Description
Salvatore Brigaglia
2009-06-16 10:26:38 UTC
Andreas, It's clear here. Exiv2 crash when reading JPEG file. Talking with Salvatore from IRC, he use Exiv2 0.18.1 This evening, he will try to use trunk code. If digiKam crash again, he will try to identify which image is in case Gilles Caulier Ok. He can just identify the image and attach it here or send it to me. Judging from the backtrace, I believe this will also happen with the trunk code. Andreas Tried again with exiv2 from trunk. The crash is the same: Application: digiKam (digikam), signal: Aborted [Current thread is 1 (Thread 0xb446e710 (LWP 23998))] Thread 14 (Thread 0xb2bc3b70 (LWP 23999)): [KCrash Handler] #6 0xffffe424 in __kernel_vsyscall () #7 0xb522b43f in raise () from /lib/libc.so.6 #8 0xb522cd86 in abort () from /lib/libc.so.6 #9 0xb526df8d in ?? () from /lib/libc.so.6 #10 0xb52729f9 in free () from /lib/libc.so.6 #11 0xb553e16b in qFree(void*) () from /usr/lib/libQtCore.so.4 #12 0xb558be62 in QString::free(QString::Data*) () from /usr/lib/libQtCore.so.4 #13 0xb55c6c61 in ?? () from /usr/lib/libQtCore.so.4 #14 0xb55c7839 in ?? () from /usr/lib/libQtCore.so.4 #15 0xb55c7d2b in QDirIterator::next() () from /usr/lib/libQtCore.so.4 #16 0xb55b9f90 in QAbstractFileEngine::entryList(QFlags<QDir::Filter>, QStringList const&) const () from /usr/lib/libQtCore.so.4 #17 0xb560c6a4 in QFSFileEngine::entryList(QFlags<QDir::Filter>, QStringList const&) const () from /usr/lib/libQtCore.so.4 #18 0xb55c0334 in QDir::entryInfoList(QStringList const&, QFlags<QDir::Filter>, QFlags<QDir::SortFlag>) const () from /usr/lib/libQtCore.so.4 #19 0xb55c0574 in QDir::entryInfoList(QFlags<QDir::Filter>, QFlags<QDir::SortFlag>) const () from /usr/lib/libQtCore.so.4 #20 0xb6de8b71 in Digikam::CollectionScanner::scanAlbum (this=0xb2bc32f0, location=@0xb2bc3230, album=@0xb2bc2ec8) at /home/tore/source/graphics/digikam/libs/database/collectionscanner.cpp:538 #21 0xb6de9166 in Digikam::CollectionScanner::scanAlbum (this=0xb2bc32f0, location=@0xb2bc3230, album=@0xb2bc2fe8) at /home/tore/source/graphics/digikam/libs/database/collectionscanner.cpp:603 #22 0xb6de9166 in Digikam::CollectionScanner::scanAlbum (this=0xb2bc32f0, location=@0xb2bc3230, album=@0xb2bc3108) at /home/tore/source/graphics/digikam/libs/database/collectionscanner.cpp:603 #23 0xb6de9166 in Digikam::CollectionScanner::scanAlbum (this=0xb2bc32f0, location=@0xb2bc3230, album=@0xb2bc31e8) at /home/tore/source/graphics/digikam/libs/database/collectionscanner.cpp:603 #24 0xb6de7ab3 in Digikam::CollectionScanner::scanAlbumRoot (this=0xb2bc32f0, location=@0xb2bc3230) at /home/tore/source/graphics/digikam/libs/database/collectionscanner.cpp:392 #25 0xb6de71d9 in Digikam::CollectionScanner::partialScan (this=0xb2bc32f0, albumRoot=@0xb2bc32bc, album=@0xb2bc32b8) at /home/tore/source/graphics/digikam/libs/database/collectionscanner.cpp:302 #26 0xb6de6df5 in Digikam::CollectionScanner::partialScan (this=0xb2bc32f0, filePath=@0xb2bc3314) at /home/tore/source/graphics/digikam/libs/database/collectionscanner.cpp:256 #27 0x082db5a2 in Digikam::ScanController::run (this=0x85a8040) at /home/tore/source/graphics/digikam/digikam/scancontroller.cpp:487 #28 0xb5543a6f in ?? () from /usr/lib/libQtCore.so.4 #29 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #30 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 13 (Thread 0xb2276b70 (LWP 24001)): #0 0xb4d872cb in clock_gettime () from /lib/librt.so.1 #1 0xb566a4ec in ?? () from /usr/lib/libQtCore.so.4 #2 0xb566a732 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb566af02 in ?? () from /usr/lib/libQtCore.so.4 #4 0xb5668be3 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb4cf95b8 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #6 0xb4cf9959 in ?? () from /usr/lib/libglib-2.0.so.0 #7 0xb4cf9eae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #8 0xb5668a37 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #9 0xb563ac1d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #10 0xb563b069 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #11 0xb5540717 in QThread::exec() () from /usr/lib/libQtCore.so.4 #12 0xb6e517e5 in Digikam::ImageFilterModelWorker::Thread::run (this=0x84c3478) at /home/tore/source/graphics/digikam/libs/models/imagefiltermodelthreads.h:66 #13 0xb5543a6f in ?? () from /usr/lib/libQtCore.so.4 #14 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #15 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 12 (Thread 0xb193fb70 (LWP 24002)): #0 0xb54a6d2c in pthread_mutex_lock () from /lib/libpthread.so.0 #1 0xb4cf95ef in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0xb4cf9959 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0xb4cf9eae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0xb5668a37 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #5 0xb563ac1d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #6 0xb563b069 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #7 0xb5540717 in QThread::exec() () from /usr/lib/libQtCore.so.4 #8 0xb6e517e5 in Digikam::ImageFilterModelWorker::Thread::run (this=0x85984d0) at /home/tore/source/graphics/digikam/libs/models/imagefiltermodelthreads.h:66 #9 0xb5543a6f in ?? () from /usr/lib/libQtCore.so.4 #10 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #11 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 11 (Thread 0xb1111b70 (LWP 24003)): #0 0xb51b8868 in ?? () from /usr/lib/libjpeg.so.62 #1 0xb51bb41e in ?? () from /usr/lib/libjpeg.so.62 #2 0xb51ba4a3 in ?? () from /usr/lib/libjpeg.so.62 #3 0xb51b42f3 in jpeg_read_scanlines () from /usr/lib/libjpeg.so.62 #4 0xb701dca9 in Digikam::loadJPEGScaled (image=@0xb1110fb4, path=@0xb1110fc0, maximumSize=256) at /home/tore/source/graphics/digikam/libs/jpegutils/jpegutils.cpp:222 #5 0xb709012f in Digikam::ThumbnailCreator::createThumbnail (this=0x85fb7c8, info=@0xb11110a8) at /home/tore/source/graphics/digikam/libs/threadimageio/thumbnailcreator.cpp:284 #6 0xb708f84d in Digikam::ThumbnailCreator::load (this=0x85fb7c8, path=@0x95e98a4) at /home/tore/source/graphics/digikam/libs/threadimageio/thumbnailcreator.cpp:192 #7 0xb7098323 in Digikam::ThumbnailLoadingTask::execute (this=0x95e9898) at /home/tore/source/graphics/digikam/libs/threadimageio/thumbnailtask.cpp:135 #8 0xb707e454 in Digikam::LoadSaveThread::run (this=0x8636c00) at /home/tore/source/graphics/digikam/libs/threadimageio/loadsavethread.cpp:139 #9 0xb5543a6f in ?? () from /usr/lib/libQtCore.so.4 #10 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #11 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 10 (Thread 0xb0910b70 (LWP 24004)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb54a8df5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb5544bc0 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #3 0xb707e407 in Digikam::LoadSaveThread::run (this=0x85d9520) at /home/tore/source/graphics/digikam/libs/threadimageio/loadsavethread.cpp:136 #4 0xb5543a6f in ?? () from /usr/lib/libQtCore.so.4 #5 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #6 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 9 (Thread 0xad9c4b70 (LWP 24005)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb54a9122 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xaea17721 in ?? () from /usr/lib/libxine.so.1 #3 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #4 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 8 (Thread 0xaccf1b70 (LWP 24006)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb54a9122 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xaea2617e in ?? () from /usr/lib/libxine.so.1 #3 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #4 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 7 (Thread 0xac4f0b70 (LWP 24007)): #0 0xb4d872cb in clock_gettime () from /lib/librt.so.1 #1 0xb566a4ec in ?? () from /usr/lib/libQtCore.so.4 #2 0xb566a732 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb566af02 in ?? () from /usr/lib/libQtCore.so.4 #4 0xb5668be3 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb4cf95b8 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #6 0xb4cf9959 in ?? () from /usr/lib/libglib-2.0.so.0 #7 0xb4cf9eae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #8 0xb5668a37 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #9 0xb563ac1d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #10 0xb563b069 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #11 0xb5540717 in QThread::exec() () from /usr/lib/libQtCore.so.4 #12 0xaea6d5b8 in Phonon::MediaSource::type() const () from /usr/lib/kde4/plugins/phonon_backend/phonon_xine.so #13 0xb5543a6f in ?? () from /usr/lib/libQtCore.so.4 #14 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #15 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 6 (Thread 0xabcefb70 (LWP 24008)): #0 0xb52e1638 in ?? () from /lib/libc.so.6 #1 0xb52c8f57 in poll () from /lib/libc.so.6 #2 0xad175536 in ?? () from /usr/lib/libpulse.so.0 #3 0xad162c60 in pa_mainloop_poll () from /usr/lib/libpulse.so.0 #4 0xad1643bd in pa_mainloop_iterate () from /usr/lib/libpulse.so.0 #5 0xad1644a4 in pa_mainloop_run () from /usr/lib/libpulse.so.0 #6 0xad17541e in ?? () from /usr/lib/libpulse.so.0 #7 0xad135613 in ?? () from /usr/lib/libpulsecommon-0.9.15.so #8 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #9 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 5 (Thread 0xa74edb70 (LWP 24009)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb54a8df5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xaea29f33 in ?? () from /usr/lib/libxine.so.1 #3 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #4 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 4 (Thread 0xa6cb7b70 (LWP 24010)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb54a8df5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb5544bc0 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #3 0xb707e407 in Digikam::LoadSaveThread::run (this=0x8e940b8) at /home/tore/source/graphics/digikam/libs/threadimageio/loadsavethread.cpp:136 #4 0xb5543a6f in ?? () from /usr/lib/libQtCore.so.4 #5 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #6 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 3 (Thread 0xa6164b70 (LWP 24011)): #0 0xb4d872cb in clock_gettime () from /lib/librt.so.1 #1 0xb566a4ec in ?? () from /usr/lib/libQtCore.so.4 #2 0xb566a732 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb566af02 in ?? () from /usr/lib/libQtCore.so.4 #4 0xb5668be3 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb4cf95b8 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #6 0xb4cf9959 in ?? () from /usr/lib/libglib-2.0.so.0 #7 0xb4cf9eae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #8 0xb5668a37 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #9 0xb563ac1d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #10 0xb563b069 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #11 0xb5540717 in QThread::exec() () from /usr/lib/libQtCore.so.4 #12 0x082d2d1d in Digikam::MetadataManagerWorker::Thread::run (this=0x911b200) at /home/tore/source/graphics/build/digikam/digikam/../../../digikam/digikam/metadatamanager_p.h:145 #13 0xb5543a6f in ?? () from /usr/lib/libQtCore.so.4 #14 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #15 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 2 (Thread 0xa5963b70 (LWP 24012)): #0 0xb54a6d23 in pthread_mutex_lock () from /lib/libpthread.so.0 #1 0xb4cf7f97 in g_main_context_release () from /usr/lib/libglib-2.0.so.0 #2 0xb4cf9a96 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0xb4cf9eae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0xb5668a37 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #5 0xb563ac1d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #6 0xb563b069 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #7 0xb5540717 in QThread::exec() () from /usr/lib/libQtCore.so.4 #8 0x082d2d1d in Digikam::MetadataManagerWorker::Thread::run (this=0x9117220) at /home/tore/source/graphics/build/digikam/digikam/../../../digikam/digikam/metadatamanager_p.h:145 #9 0xb5543a6f in ?? () from /usr/lib/libQtCore.so.4 #10 0xb54a46f5 in start_thread () from /lib/libpthread.so.0 #11 0xb54a4610 in ?? () from /lib/libpthread.so.0 Thread 1 (Thread 0xb446e710 (LWP 23998)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb52c8f6e in poll () from /lib/libc.so.6 #2 0xb480e150 in ?? () from /usr/lib/libxcb.so.1 #3 0xb480e6f2 in ?? () from /usr/lib/libxcb.so.1 #4 0xb480eac1 in xcb_writev () from /usr/lib/libxcb.so.1 #5 0xb504984c in _XSend () from /usr/lib/libX11.so.6 #6 0xb5049e70 in _XEventsQueued () from /usr/lib/libX11.so.6 #7 0xb50322f4 in XEventsQueued () from /usr/lib/libX11.so.6 #8 0xb5bd850d in ?? () from /usr/lib/libQtGui.so.4 #9 0xb4cf95b8 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #10 0xb4cf9959 in ?? () from /usr/lib/libglib-2.0.so.0 #11 0xb4cf9eae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #12 0xb56689e8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #13 0xb5bd829a in ?? () from /usr/lib/libQtGui.so.4 #14 0xb563ac1d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #15 0xb563b069 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #16 0xb563d430 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #17 0xb5b35894 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #18 0x0830c819 in main (argc=5, argv=0xbfaa9bf4) at /home/tore/source/graphics/digikam/digikam/main.cpp:184 How do i understand whatimage is crashing digiKam? I found a lot of images that return a string like: "Error: Directory Canon: Next pointer is out of bounds; ignored." Being that images just downloaded i blamed them for crashing digiKam. But the crash tonight occurred while scanning also a folder i had for months! Salvatore, That backtrace is different. This time, the crash is definitely not from Exiv2. > "Error: Directory Canon: Next pointer is out of bounds; ignored." You can ignore this. It doesn't do any harm. It means that Exiv2 has detected something wrong with the metadata structure in the image. But Exiv2 can work around this just fine. > How do i understand whatimage is crashing digiKam? For a start, just run the exiv2 command line tool over your images and if it crashes, you should be able to see which image caused the problem: $ cd <IMGFOLDER> $ exiv2 -pa * Andreas There are some other reports here with the crash when freeing memory in QDir code. All with KDE4.3beta. It could be a memory corruption occurring somewhere. that's the situatio now: digiKam, exiv2, libkexiv2, libkdcraw from actual developments branches. All updated at least one hour ago. digiKam components: digiKam version 1.0.0-beta2 (rev.: 983954) Exiv2 can write to Pgf: No Exiv2 può scrivere Jp2: Sì Exiv2 può scrivere Jpeg: Sì Exiv2 può scrivere Png: Sì Exiv2 può scrivere Tiff: Sì Exiv2 supports XMP metadata: Sì LibCImg: 130 LibExiv2: 0.18.1 LibJPEG: 62 LibJasper: 1.900.1 LibKDE: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) "release 138" LibKExiv2: 0.6.0 LibKdcraw: 0.5.0 LibLCMS: 118 LibPGF: 6.09.24 LibPNG: 1.2.37 LibQt: 4.5.1 LibRaw: 0.7.2 LibTIFF: LIBTIFF, Version 3.8.2 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Oggetto Marble: 0.8SVN Parallelized demosaicing: Sì LibGphoto2: 2.4.6.1 LibKipi: 0.4.0 All configs deleted, digiKam runs fine under gdb for the firs time. Wizard is completed and firs scan of the collection ended succesfully. Trying to enter the collection to see some pictures and no thumbnails are shown. 1) NO ITEM IS SHOWN AT ALL IN THE ICON VIEW then i rebuild manually all thumbnails from the menu and digiKam crashes with this backtrace from gdb: http://pastebin.ca/1466392 then, triyng to start again digikam it ALWAYS crashes if started from krunner: http://pastebin.ca/1466400 But if started from konsole it runs, but nothing is shown on iconview and it crashes when re-building thumbnails: http://pastebin.ca/1466405 I'm lost. Salvatore : This is a package problem from Debian stuff. look these files - 195975 - 195079 It's relevant of Marble package which broken binary compatibility. To solve it, checkout marble code from svn, and recompile and install it. after that, recompile and install digiKam. This must solve the problem. Anyway, we lost a lots of time duing wrong packaging, especially with not stable code from KDE4. No blame here, but you must understand that you cannot update whole KDE4 from KDE 4.2.x to KDE 4.3.x without side effect. open source is like closed here : bugs are bugs... Gilles Caulier (In reply to comment #7) > Salvatore : > > This is a package problem from Debian stuff. look these files > I'm on openSUSE 11.2 Milestone 2 scheduled to be released with KDE 4.3 in october. Shouldn't digiKam be friendly to that? > > It's relevant of Marble package which broken binary compatibility. To solve it, > checkout marble code from svn, and recompile and install it. after that, > recompile and install digiKam. This must solve the problem. Done that yesterday night. I'll try to compile digiKam without marblewidget to see if it solve the problems. > > Anyway, we lost a lots of time duing wrong packaging, especially with not > stable code from KDE4. > > No blame here, but you must understand that you cannot update whole KDE4 from > KDE 4.2.x to KDE 4.3.x without side effect. open source is like closed here : > bugs are bugs... That's why i'm running code from trunk, to help you to find problems. I can install a stable system if i need stability. I think that being KDE 4.3 in beta stage digiKam should start to run fine also here... Anyway trying to compile without marble support, let's see what happens. Tell me if you want me to stop trying that. yes, let's go. If without marble, it run fine, please report to marble team to respect compatibility issues. I have fork a a lots of bugs to marble since a long time now. But it sound like marble team prefer to implement again and again and again new features without to take a care about compatibilities. MArble is not only a stand alone application. It's a shared widget. all library rules must be applied here. Gilles Caulier Reconsider my whish then ;) https://bugs.kde.org/show_bug.cgi?id=196678 Gilles, compiled without marble is the same. Crashes every now and then when scanning images or reading thumbnails. But while reading a bug about amarok i was inspired to start digiKam setting the MALLOC_CHECK_ variable to 0 result, digiKam is working. What this points to? MALLOC_CHECK_ variable to 0 ??? What is that ? Gilles Caulier (In reply to comment #12) > MALLOC_CHECK_ variable to 0 ??? > > What is that ? > > Gilles Caulier I don't know but now digiKam is HAPPY! Let me point you to some links. I really Can't understand what malloc is... https://bugs.kde.org/show_bug.cgi?id=191447 http://www.linuxquestions.org/questions/linux-general-1/why-malloccheck-628856/ Hope it helps. Thanks Salvatore. your links help. Well, to resume this file, i can said this is a specific problem from linux distro which do not set MALLOC_CHECK_ to 0 or 1 with no stable version of programs as KDE 4.3-beta. Gilles Caulier it seems it is a decision of the kde team. It is clearly indicated in the startkde script: *** # Enable lightweight memory corruption checker -- this is for trunk only, we remove it for releases MALLOC_CHECK_=2 export MALLOC_CHECK_ *** Salvatore, If you can run digikam in valgrind, this will probably give a more precise pointer where exactly the problem is. Gilles, Is there anything particular that needs to be observed for that? Andreas (In reply to comment #16) > Salvatore, > > If you can run digikam in valgrind, this will probably give a more precise > pointer where exactly the problem is. > Is valgrind a tool like gdb? How should i run it? Look HACKING file for details. Gilles Valgrind rocks! It is a program for debugging Linux executables. It is very easy to use and particularly useful for profiling and to detect memory management bugs. Especially those nasty ones which are otherwise very hard to catch. It complements gdb. I often run valgrind first and then step through the code that it pointed out using gdb. Andreas |