Version: 0.10.0 (using KDE 4.2.2) Compiler: GCC 4.3 OS: Linux Installed from: Ubuntu Packages Apparently, digikam 0.10.0 can't handle big collections. It already crashed when reading in a 200 Mib directory (which is just a small portion of my collection). I've played arround with several subdirectories of my whole collection, always with the same result: digikam crashes as soon as digikam4.db exceeds 11 Mib.
Created attachment 32915 [details] Backtrace
Created attachment 32916 [details] Backtrace
Created attachment 32917 [details] Backtrace
Please file us a GDB backtrace in text, running digiKam from a console, like it's explained here : http://www.digikam.org/contrib Gilles Caulier
Created attachment 32919 [details] A Backtrace with gdb Sorry, thought the kcrashhandler backtraces would be sufficient.
The problem is not the directory size, but some images seem to be corrupt? At least the crash happens in exiv2 lib during file reading. I have a folder with 1GB of files in it, no problem so far. Can you start digiKam from a console and check the file that causes the crash? There should be some output. Try to move this file out of the folder and see if it is working. Andi
Yes, it's another crash relevant of Exiv2. Please update to last stable 0.18.1. libkexiv2, digiKam and kipi-plugins need to be recompiled Gilles Caulier
May be the same as 189982. At least it's both exiv2's fault.
*** This bug has been marked as a duplicate of bug 189982 ***
Fixed with bug #189982