Bug 135051 - digikam crashes when building database from existing directory
Summary: digikam crashes when building database from existing directory
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-03 17:50 UTC by Janet
Modified: 2019-12-25 15:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.0.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janet 2006-10-03 17:50:05 UTC
Version:           0.9.0-beta2-1 (using KDE KDE 3.5.4)
Installed from:    Debian testing/unstable Packages
OS:                Linux

My picture folder is about 30 GB (13883 files, 335 subfolders). Now I wanted to use this folder as base folder for digikam. But it crashes building the database (at about 12-13%). Started from konsole I just get this:
 
Warning: Makernote IFD has a next pointer != 0 (1330401091). Ignored.
Warning: Makernote IFD has a next pointer != 0 (1330401091). Ignored.
Warning: Makernote IFD has a next pointer != 0 (1330401091). Ignored.
Warning: Makernote IFD has a next pointer != 0 (1330401091). Ignored.
KCrash: Application 'digikam' crashing...
    
The KDE crashmanager gives me:
          [KCrash handler]
#5  0xb619b2ad in mallopt () from /lib/tls/libc.so.6
#6  0xb619b942 in free () from /lib/tls/libc.so.6
#7  0xb633d591 in operator delete () from /usr/lib/libstdc++.so.6
#8  0xb631a11d in std::string::_Rep::_M_destroy ()
   from /usr/lib/libstdc++.so.6
#9  0xb7eec466 in Digikam::DMetadata::convertCommentValue ()
   from /usr/lib/libdigikam.so.0
#10 0xb7eee056 in Digikam::DMetadata::getImageComment ()
   from /usr/lib/libdigikam.so.0
#11 0xb7d59db7 in Digikam::ScanLib::storeItemInDatabase ()
   from /usr/lib/libdigikam.so.0
#12 0xb7d5b679 in Digikam::ScanLib::allFiles () from /usr/lib/libdigikam.so.0
#13 0xb7d5b62c in Digikam::ScanLib::allFiles () from /usr/lib/libdigikam.so.0
#14 0xb7d5b62c in Digikam::ScanLib::allFiles () from /usr/lib/libdigikam.so.0
#15 0xb7d5beb3 in Digikam::ScanLib::findMissingItems ()
   from /usr/lib/libdigikam.so.0
#16 0xb7d5c137 in Digikam::ScanLib::startScan () from /usr/lib/libdigikam.so.0
#17 0xb7cf8ad8 in Digikam::AlbumManager::setLibraryPath ()
   from /usr/lib/libdigikam.so.0
#18 0x0804a36b in main ()
Comment 1 caulier.gilles 2006-10-03 18:27:16 UTC
Problem already reported. Investiguations under progress.

Gilles Caulier

*** This bug has been marked as a duplicate of 134999 ***
Comment 2 caulier.gilles 2019-12-25 15:51:25 UTC
Not reproducible using digiKam 7.0.0 beta1.