| Summary: | Segmentation fault - QMutex::lock() | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Don Curtis <bugrprt21882> |
| Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/digikam/fd50357b4853cdeb0272f284f58315d1a7e588d0 | Version Fixed/Implemented In: | 5.9.0 |
| Sentry Crash Report: | |||
|
Description
Don Curtis
2018-02-12 16:21:44 UTC
1/ Run digiKam into GDB to see where the program crash exactly : https://www.digikam.org/contribute/ 2/ Try to use the Linux AppImage bundle instead to see if crash is reproducible : https://files.kde.org/digikam/ Gilles Caulier digikam.database: Pick Label found : 0 digikam.database: Assigned Pick Label Tag : 16 digikam.database: Color Label found : 0 digikam.database: Assigned Color Label Tag : 6 digikam.metaengine: Loading image history "" digikam.database: Scanning took 84 ms digikam.database: Finishing took 227 ms digikam.general: Cancel Main Thread [Thread 0x7ffeebfff700 (LWP 3147) exited] Detaching after fork from child process 3155. digikam.general: Event is dispatched to desktop notifier through DBUS digikam.general: Cancel Main Thread digikam.general: List of Pending Jobs is empty digikam.general: Cancel Main Thread digikam.general: Cancel Main Thread digikam.dimg: "/home01/Bilder/bilder01/Bilder/Digitalkamera/2012/2012-04-28/SDIM3093.jpg" : JPEG file identified digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2012-04-28 12:18:01.000 CEST Qt::TimeSpec(LocalTime)) digikam.metaengine: DateTime (Exif digitalized): So. Juli 1 18:01:28 2012 digikam.metaengine: Orientation => Exif.Image.Orientation => 1 digikam.metaengine: "/home01/Bilder/bilder01/Bilder/Digitalkamera/2012/2012-04-28/SDIM3093.jpg" ==> Read Iptc Keywords: () digikam.database: Pick Label found : 0 digikam.database: Assigned Pick Label Tag : 16 digikam.database: Color Label found : 0 digikam.database: Assigned Color Label Tag : 6 digikam.metaengine: Loading image history "" digikam.database: Scanning took 76 ms digikam.database: Finishing took 200 ms Thread 170 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffeeb7fe700 (LWP 3148)] 0x00007ffff408e445 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5 (gdb) bt #0 0x00007ffff408e445 in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #1 0x00007ffff76a3d6e in () at /usr/lib64/libdigikamgui.so.5.8.0 #2 0x00007ffff76a5437 in () at /usr/lib64/libdigikamgui.so.5.8.0 #3 0x00007ffff409285e in () at /usr/lib64/libQt5Core.so.5 #4 0x00007ffff4095a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x00007fffefd57724 in start_thread () at /lib64/libpthread.so.0 #6 0x00007ffff33afc1d in clone () at /lib64/libc.so.6 (gdb) Same scenario: Extras; Maintenance; stop the generation of new thumbnails or, update Metadata entries in the database. openSUSE Leap 42.3 plasmashell 5.8.7 KDE Frameworks: 5.32.0 Qt: 5.6.2 I can not reproduce it here. On openSUSE Leap-42.3 with the digiKam from the repository I can test it tomorrow in the company if it is reproducible. Please test it in any case with the AppImage. Maik The problem is here reproducible with openSUSE Leap-42.3 and the digiKam version of the repository. Gilles, do you have a digiKam version for testing with Qt-5.6.2 available? I'll check tonight if there's a possible cause in digiKam.
(gdb) bt
#0 0x00007ffff408e445 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5
#1 0x00007ffff76a3d6e in Digikam::MaintenanceData::getImageInfo (this=0x448dfa0)
at /usr/src/debug/digikam-5.8.0/core/utilities/maintenance/maintenancedata.cpp:133
#2 0x00007ffff76a5437 in Digikam::MetadataTask::run (this=0x2032200)
at /usr/src/debug/digikam-5.8.0/core/utilities/maintenance/metadatatask.cpp:95
#3 0x00007ffff409285e in ?? () from /usr/lib64/libQt5Core.so.5
#4 0x00007ffff4095a29 in ?? () from /usr/lib64/libQt5Core.so.5
#5 0x00007fffefd57724 in start_thread () from /lib64/libpthread.so.0
#6 0x00007ffff33afc1d in clone () from /lib64/libc.so.6
Maik
My 5.8.0 (or master) here running under Mageai6 use Qt 5.6.2 and the problem is not reproducible. Gilles (In reply to caulier.gilles from comment #6) > My 5.8.0 (or master) here running under Mageai6 use Qt 5.6.2 and the problem > is not reproducible. > > Gilles Given what's been reported here it seems that, it may be something which is only misbehaving on AMD (FX(tm)-4100 Quad-Core) (my platform -- haven't tried to reproduce it on a Lenovo AMD Notebook) and the openSUSE Leap 42.3 distribution. Given that, Leap 15 will be coming in May this year my suggestion is, to wait at least until then and, I'll check the behaviour on another AMD platform later today and, will report this evening CET. Cheers. It has nothing to do with the processor, my laptop in the company has an Intel. I think I can fix it without reproducing it. I think we can simplify a lot with the cancel feature in the maintenance tool. Although the changes are quite extensive, I will still integrate them into digiKam-5.9.0. Maik Git commit fd50357b4853cdeb0272f284f58315d1a7e588d0 by Maik Qualmann. Committed on 13/02/2018 at 20:26. Pushed by mqualmann into branch 'master'. optimize cancel function of the maintenance tools FIXED-IN: 5.9.0 M +2 -2 NEWS M +15 -19 utilities/maintenance/databasetask.cpp M +1 -1 utilities/maintenance/databasetask.h M +9 -13 utilities/maintenance/fingerprintstask.cpp M +1 -5 utilities/maintenance/fingerprintstask.h M +9 -10 utilities/maintenance/imagequalitytask.cpp M +1 -1 utilities/maintenance/imagequalitytask.h M +2 -26 utilities/maintenance/maintenancethread.cpp M +11 -18 utilities/maintenance/metadatatask.cpp M +1 -5 utilities/maintenance/metadatatask.h M +10 -13 utilities/maintenance/thumbstask.cpp M +1 -5 utilities/maintenance/thumbstask.h https://commits.kde.org/digikam/fd50357b4853cdeb0272f284f58315d1a7e588d0 Don, Tomorrow morning, i will rebuild the 5.9.0 AppImage Linux pre-release bundle. It will be automatically uploaded here : https://files.kde.org/digikam/ Build take few hours be patient to check when the bundle list is updated. You will be able to test the Maik fix quickly. AppImage do not install files on your system. It's a self executable with all dependencies included inside. Gilles Caulier The new item finder crashes when it is canceled. This is independent of the last patch. I will fix it tonight. Maik Git commit 789c51fba6bb49408dda7924441a466bf5652cf6 by Maik Qualmann. Committed on 14/02/2018 at 19:24. Pushed by mqualmann into branch 'master'. leave QEventLoop from the ScanController if scan canceled, to fix crash from the new item finder M +4 -0 libs/database/utils/scancontroller.cpp M +1 -0 libs/database/utils/scancontroller.h M +20 -2 utilities/maintenance/newitemsfinder.cpp https://commits.kde.org/digikam/789c51fba6bb49408dda7924441a466bf5652cf6 |