[digikam] [Bug 425703] DigiKam crashes (again) under Linux while detecting faces
https://bugs.kde.org/show_bug.cgi?id=425703 kamu changed: What|Removed |Added Version|7.0.0 |7.2.0 --- Comment #3 from kamu --- Sure. Unfortunately there's a crash again. What I did: $ export QT_LOGGING_RULES="digikam*=true" $ digikam-7.2.0-beta1-20200928T085016-x86-64-debug.appimage debug What I got: Digikam::DNNFaceDetectorBase::selectBbox: Good rect = QRect(128,112 25x34) , conf = 0.946965 Digikam::DetectionWorker::process: Found 1 faces in "IMG-20200817-WA0027.jpg" QSize(1200, 1600) QSize(1200, 1600) Digikam::ActionThreadBase::cancel: Cancel Main Thread Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using 6 CPU core to run threads Digikam::DetectionWorker::process: Found 0 faces in "IMG-20200818-WA.jpg" QSize(1200, 1600) QSize(1200, 1600) [New Thread 0x7fff38ff9700 (LWP 6571)] [Thread 0x7fff13fff700 (LWP 6568) exited] [Thread 0x7fff38ff9700 (LWP 6570) exited] Thread 435 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff3bfff700 (LWP 5974)] 0x773c61d4 in Digikam::PreviewLoadingTask::execute (this=0xc5e10b0) at /b/dktemp/digikam-master/core/libs/threadimageio/preview/previewtask.cpp:347 347 /b/dktemp/digikam-master/core/libs/threadimageio/preview/previewtask.cpp: No such file or directory. (gdb) bt #0 0x773c61d4 in Digikam::PreviewLoadingTask::execute (this=0xc5e10b0) at /b/dktemp/digikam-master/core/libs/threadimageio/preview/previewtask.cpp:347 #1 0x773dc25e in Digikam::LoadSaveThread::run (this=0xcc97a80) at /b/dktemp/digikam-master/core/libs/threadimageio/fileio/loadsavethread.cpp:154 #2 0x774015ee in Digikam::DynamicThread::Private::run (this=0x3658ca0) at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:191 #3 0x741a8d87 in ?? () from /tmp/.mount_digikaN5vePI/usr/lib/libQt5Core.so.5 #4 0x741a5335 in ?? () from /tmp/.mount_digikaN5vePI/usr/lib/libQt5Core.so.5 #5 0x7333e6db in start_thread (arg=0x7fff3bfff700) at pthread_create.c:463 #6 0x73067a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 kamu changed: What|Removed |Added Platform|unspecified |Appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] New: DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 Bug ID: 425698 Summary: DigiKam face detection crash under Linux Product: digikam Version: 7.0.0 Platform: unspecified OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: k...@turnbeutel-vergesser.com Target Milestone: --- Created attachment 13 --> https://bugs.kde.org/attachment.cgi?id=13&action=edit gdb log and backtrace SUMMARY STEPS TO REPRODUCE 1. run digikam-7.0.0-x86-64.appimage debug (downloaded August 12th 2020) 2. start face detection, skipping already processed files 3. observe some (low single digit) percentage of the progressbar advancing OBSERVED RESULT Crash due to double-free (see gdb excerpt attached). EXPECTED RESULT DigiKam should finish face detection without crashing. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Ubuntu 18.04.5 LTS KDE Plasma Version: - KDE Frameworks Version: - Qt Version: the one bundled in the appimage (Qt5.14.2 according to lib in image?) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 kamu changed: What|Removed |Added CC||kamu@turnbeutel-vergesser.c ||om -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 --- Comment #2 from kamu --- I'm on AMD (Phenom 1090T 6 core). Yes, I did produce that backtrace with the appimage internal debugging (using "debug" to run it). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425702] New: DigiKam crashes under Linux when detecting faces
https://bugs.kde.org/show_bug.cgi?id=425702 Bug ID: 425702 Summary: DigiKam crashes under Linux when detecting faces Product: digikam Version: 7.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: k...@turnbeutel-vergesser.com Target Milestone: --- Created attachment 131113 --> https://bugs.kde.org/attachment.cgi?id=131113&action=edit log of appimage gdb SUMMARY STEPS TO REPRODUCE 1. run "digikam-7.0.0-x86-64.appimage debug" 2. start face detection (skip already processed images) 3. let it run for some percent of the progress indicator OBSERVED RESULT crash (see gbd backtrace) EXPECTED RESULT DigiKam should finish scanning for faces SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Ubuntu 18.0.5 (available in About System) KDE Plasma Version: - KDE Frameworks Version: - Qt Version: contained in appimage ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 kamu changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=425702 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 --- Comment #4 from kamu --- The ticket looks similar, because I created them both in short succession =;-). But this one is a double free in a variant, the other one a metadata sigsev. Also the code segment locations in libdigikamcore.so.7.0.0 are quite far apart. So I think these are two distinct bugs. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 --- Comment #5 from kamu --- Do you guys store symbol information for your release builds by any chance? Sorry, I never worked with the KDE code base before... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425703] New: DigiKam crashes (again) under Linux while detecting faces
https://bugs.kde.org/show_bug.cgi?id=425703 Bug ID: 425703 Summary: DigiKam crashes (again) under Linux while detecting faces Product: digikam Version: 7.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: k...@turnbeutel-vergesser.com Target Milestone: --- Created attachment 131115 --> https://bugs.kde.org/attachment.cgi?id=131115&action=edit crash in LoadSaveThread SUMMARY STEPS TO REPRODUCE 1. run "digikam-7.0.0-x86-64.appimage debug" 2. start face detection (skip already processed images) 3. let it run for some percent of the progress indicator OBSERVED RESULT crash (see gbd backtrace) EXPECTED RESULT DigiKam should finish scanning for faces SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Ubuntu 18.0.5 (available in About System) KDE Plasma Version: - KDE Frameworks Version: - Qt Version: contained in appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 --- Comment #9 from kamu --- Cool, thank you! I'll try to reproduce some crashes with the debug bundle. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 --- Comment #10 from kamu --- Just as additional information: I use 2.8 out of 8GB RAM, so I don't think this is due to memory pressure. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 --- Comment #12 from kamu --- Created attachment 131125 --> https://bugs.kde.org/attachment.cgi?id=131125&action=edit Memory usage while scanning for faces No it looks like I _do_ have a problem with exhausted memory. My 8GB were eaten up completely while waiting for the debug build to crash. Is there anything I could do to prevent that? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425698] DigiKam face detection crash under Linux
https://bugs.kde.org/show_bug.cgi?id=425698 --- Comment #14 from kamu --- Created attachment 131128 --> https://bugs.kde.org/attachment.cgi?id=131128&action=edit gdb backtrace from debug bundle Ok, it ain't much, but it's honest work. Caught a crash with the debug bundle and memory was steady at 2.5GB, so no out of memory condition with this one. The first two stack frames had no locals, so I printed the first frame that did, hope it is not totally useless... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402322] During face detection, the "People" / "Unconfirmed" (or "Unknown") tab content keeps jumping around
https://bugs.kde.org/show_bug.cgi?id=402322 kamu changed: What|Removed |Added CC||kamu@turnbeutel-vergesser.c ||om --- Comment #13 from kamu --- I can confirm this behavior (jumping around, selecting wrong image) both with and without face detection running in the background. The version I tried is Linux digikam-7.0.0-x86-64.appimage (http://commits.kde.org/digikam/6d5a0089cd5a4b81ddd09ade8a6f5dc347eebd07). Sometimes, the image I added a people tag to, vanishes and it re-appears after some seconds(!) while the view seems to just hang. During that hang, the just typed name gets displayed under the next image that has been shifted to the location of the vanished one (where the mouse is), If I then accidentally click, I seem to tag that next/wrong image with the old tag. If the image would not vanish, this would probably not happen. The long time it hangs might be a separate issue perhaps, or it is caused by that unnecessary view update and is the same issue. -- You are receiving this mail because: You are watching all bug changes.
