https://bugs.kde.org/show_bug.cgi?id=420334
--- Comment #26 from Stefan S <stefan.szeke...@gmail.com> --- (In reply to caulier.gilles from comment #24) > Did you use the bug version of OSX PKG installer ? Why there is no debug > symbols in your backtrace ? Where is located the thread responsible of the > crash ? I was using the https://files.kde.org/digikam/ digiKam-7.0.0-beta3-20200419T173721-MacOS-x86-64.pkg . Currently installing the digiKam-7.0.0-beta3-20200419T175921-MacOS-x86-64-debug.pkg hoping to reproduce it. The crash points to thread 46 Crashed Thread: 46 Thread (pooled) Thread 46 Crashed:: Thread (pooled) 0 libdigikamcore.7.0.0.dylib 0x0000000108a65aaf 0x108a51000 + 84655 1 libdigikamcore.7.0.0.dylib 0x0000000108ccbc27 Digikam::MetaEngine::load(QString const&) + 39 2 libdigikamcore.7.0.0.dylib 0x0000000108d1ee82 Digikam::DMetadata::load(QString const&) + 434 3 libdigikamcore.7.0.0.dylib 0x0000000108a70f44 Digikam::DImgLoader::readMetadata(QString const&) + 244 4 DImg_JPEG_Plugin.so 0x000000012229f36f 0x122297000 + 33647 5 libdigikamcore.7.0.0.dylib 0x0000000108c75931 Digikam::DImg::load(QString const&, int, Digikam::DImgLoaderObserver*, Digikam::DRawDecoding const&) + 1745 6 libdigikamcore.7.0.0.dylib 0x0000000108c76622 Digikam::DImg::load(QString const&, Digikam::DImgLoaderObserver*, Digikam::DRawDecoding const&) + 50 7 libdigikamcore.7.0.0.dylib 0x0000000108d8bbb5 0x108a51000 + 3386293 8 libdigikamcore.7.0.0.dylib 0x0000000108da5124 Digikam::LoadSaveThread::run() + 372 9 libdigikamcore.7.0.0.dylib 0x0000000108ddd4b3 0x108a51000 + 3720371 10 org.qt-project.QtCore 0x000000010a772147 0x10a755000 + 119111 11 org.qt-project.QtCore 0x000000010a76fbd4 0x10a755000 + 109524 12 libsystem_pthread.dylib 0x00007fff59b8f2eb _pthread_body + 126 13 libsystem_pthread.dylib 0x00007fff59b92249 _pthread_start + 66 14 libsystem_pthread.dylib 0x00007fff59b8e40d thread_start + 13 > > The debug bracktrace is less clear than Linux version... > > Gilles Caulier Indeed, because i installed the non-debug version. You can symbolicate crash log with the atos tool. You need to manually copy the exact .dSYM file for libdigikamcore.7.0.0.dylib - from the release build, not from the debug build, they are not equivalent as the builds on macOS are not deterministic. Next fire up atos atos -arch x86_64 -o <path to your dSYM>/libdigikamcore.7.0.0.dylib.dSYM/Contents/Resources/DWARF/libdigikamcore.7.0.0.dylib -l 0x108a51000 where 0x108a51000 is the load path of the binary from the crash log https://gist.github.com/0wnrepo/6e9ddb5f69f5e7eb09942f89c6306388 And plug in 0x0000000108ccbc27 and 0x0000000108a65aaf to se exactly what's in there. > It probably crashes in Exiv2 when loading the metadata. Probably through an > image with wrong metadata. I don't want to disappoint you, we have never > tested digiKam with such a number of imges. Through my photography hobby I > have about 60K images over the years, Gilles probably has over 100K. By > random generator, I created 200K images as a test. But millions... I think it > won't work. A fast internal MySQL DB on SSD is then mandatory anyway. Since > we keep all albums in the tree view model, from about 50K albums / folder > there is a strong performance problem... > Maik All good, I'm testing it *thoroughly*, although I only have macOS 10.14.5. -- You are receiving this mail because: You are watching all bug changes.
