[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 caulier.gil...@gmail.com changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||7.0.0 Resolution|--- |FIXED --- Comment #47 from Maik Qualmann --- This crash was fixed in bug 399923. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #46 from caulier.gil...@gmail.com --- After 3 weeks of work, i finally completed the compilation of AppImage using Qt 5.11.3 + QWebkit 5.212. New 6.1.0 pre-release AppImage bundle can be found here (64 bits only for the moment) : https://files.kde.org/digikam/ Please check if this bugzilla entry still valid. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #45 from Maik Qualmann --- OK thanks. I guessed it was Intel. You can also look into this bug 399923, it's basically the same bug report. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #44 from Mathieu --- Mark, Intel(R) Core(TM) i5 CPU M 480 @ 2.67GHz Thanks for all your work ! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #43 from Maik Qualmann --- Mathieu, which CPU has your computer, Intel or AMD? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #42 from Maik Qualmann --- Git commit 132352e8668695fd3ab2718e6184a5e794c64179 by Maik Qualmann. Committed on 27/10/2018 at 18:07. Pushed by mqualmann into branch 'master'. Reorganization DImg loading and caching from the PreviewLoadingTask Now we cache an unprocessed DImg Related: bug 399923 M +167 -213 core/libs/threadimageio/previewtask.cpp https://commits.kde.org/digikam/132352e8668695fd3ab2718e6184a5e794c64179 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #41 from Maik Qualmann --- Git commit 71fe4107faa82bd992756392e53910897ab4fc09 by Maik Qualmann. Committed on 25/10/2018 at 06:12. Pushed by mqualmann into branch 'master'. try to fix progressInfo crash Related: bug 399923 M +3-3core/libs/threadimageio/loadsavetask.cpp M +3-0core/libs/threadimageio/loadsavetask.h https://commits.kde.org/digikam/71fe4107faa82bd992756392e53910897ab4fc09 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #40 from Maik Qualmann --- Git commit bede4dcc3829b24494b4e4733579455452c62775 by Maik Qualmann. Committed on 24/10/2018 at 17:47. Pushed by mqualmann into branch 'master'. try to fix the crash in the preview task Related: bug 399923 M +26 -28 core/libs/threadimageio/previewtask.cpp https://commits.kde.org/digikam/bede4dcc3829b24494b4e4733579455452c62775 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #39 from Maik Qualmann --- Git commit 985be20fd70563bb3989cbb6670880c27f3babba by Maik Qualmann. Committed on 22/10/2018 at 05:56. Pushed by mqualmann into branch 'master'. add QMutexLocker patch again Related: bug 399923 M +36 -1core/libs/dimg/dimg.cpp M +3-0core/libs/dimg/dimg_p.h https://commits.kde.org/digikam/985be20fd70563bb3989cbb6670880c27f3babba -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #38 from Maik Qualmann --- Git commit 8e43d83ad9193f59551d95129b4b9b6183f39590 by Maik Qualmann. Committed on 21/10/2018 at 19:35. Pushed by mqualmann into branch 'master'. try to fix a possible VTable problem Related: bug 399923 M +2-1core/libs/dimg/filters/icc/icctransformfilter.cpp M +1-1core/libs/dimg/filters/icc/icctransformfilter.h M +9-2core/libs/dimg/loaders/dimgloaderobserver.h M +16 -6core/libs/threadimageio/loadsavetask.cpp M +6-6core/libs/threadimageio/loadsavetask.h M +2-1 core/utilities/assistants/expoblending/manager/expoblendingthread.cpp M +2-1core/utilities/assistants/panorama/tasks/preprocesstask.cpp M +2-1core/utilities/queuemanager/manager/batchtool.cpp https://commits.kde.org/digikam/8e43d83ad9193f59551d95129b4b9b6183f39590 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #37 from Maik Qualmann --- Git commit 4b84ca31a2f1c86fd3e980f093e296807180d129 by Maik Qualmann. Committed on 21/10/2018 at 08:07. Pushed by mqualmann into branch 'master'. try with QMutexLocker in DImg Related: bug 399923 M +36 -1core/libs/dimg/dimg.cpp M +3-3core/libs/dimg/dimg_p.h https://commits.kde.org/digikam/4b84ca31a2f1c86fd3e980f093e296807180d129 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #36 from Maik Qualmann --- Git commit b11a1a407f5069b7f47810a49ace08d1ed011e87 by Maik Qualmann. Committed on 20/10/2018 at 16:09. Pushed by mqualmann into branch 'master'. try to fix the crash with undocumented method in Qt Related: bug 399923 M +3-0core/libs/dimg/dimg_p.h https://commits.kde.org/digikam/b11a1a407f5069b7f47810a49ace08d1ed011e87 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #35 from Maik Qualmann --- Git commit f8d2d5f66532c3695211f06eb09f967ba1248986 by Maik Qualmann. Committed on 19/10/2018 at 19:40. Pushed by mqualmann into branch 'master'. close the QFile manually is better Now the memory usage for face recognition does not increase above 1GB and stays at 600-800KB Related: bug 399923 M +4-0core/libs/dimg/loaders/dimgloader.cpp https://commits.kde.org/digikam/f8d2d5f66532c3695211f06eb09f967ba1248986 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #34 from Maik Qualmann --- Git commit 83db20a5c25c31500b93ce8732ca6728ebd53b16 by Maik Qualmann. Committed on 19/10/2018 at 16:50. Pushed by mqualmann into branch 'master'. Revert "try to fix this problem, move image loaders to the heap" Related: bug 399923 M +57 -73 core/libs/dimg/dimg.cpp https://commits.kde.org/digikam/83db20a5c25c31500b93ce8732ca6728ebd53b16 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #33 from Maik Qualmann --- Git commit 807847709a3dfc4b8fb90391bc0729839af203ec by Maik Qualmann. Committed on 19/10/2018 at 10:35. Pushed by mqualmann into branch 'master'. try to fix this problem, move image loaders to the heap Related: bug 399923 M +73 -57 core/libs/dimg/dimg.cpp https://commits.kde.org/digikam/807847709a3dfc4b8fb90391bc0729839af203ec -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #32 from Mathieu --- core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 15130 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 15130 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #31 from Maik Qualmann --- Mathieu, because we see crashes in different components that we can not explain. Can you post the output of "ulimit -a"? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #30 from Mathieu --- Test: - without CM - with multi-core unfortunately, it crashes igikam::OpenCVFaceDetector::cascadeResult: detectMultiScale gave () Digikam::OpenCVFaceDetector::verifyFace: Verifying face QRect(228,134 36x36) using cascade 8 Digikam::OpenCVFaceDetector::verifyFace: feature QRectF(0.1,0.4 0.8x0.6) QRect(228,134 36x36) QRect(232,148 29x22) Digikam::OpenCVFaceDetector::cascadeResult: detectMultiScale: image size 29 22 searchIncrement 1.1 grouping 2 flags 0 min size 4 4 Digikam::OpenCVFaceDetector::cascadeResult: detectMultiScale gave () Digikam::DetectionWorker::process: Found 0 faces in "2003-06-28_00 - Divers ( (001).jpg" QSize(1917, 1242) QSize(1917, 1242) Digikam::FaceUtils::writeUnconfirmedResults: Entry QRect(319,150 164x164)53overlapsQRect(319,150 164x164)603, skipping Digikam::DImg::copy: : return null image! ( false , 0 , 0 ) Digikam::FaceUtils::writeUnconfirmedResults: Entry QRect(314,128 209x209)37overlapsQRect(312,123 223x223)603, skipping Digikam::DImg::copy: : return null image! ( false , 0 , 0 ) [New Thread 0x7fff48ff9700 (LWP 17775)] [Thread 0x7fff48ff9700 (LWP 17744) exited] Thread 102 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff497fa700 (LWP 17274)] 0x7630b50e in QSharedDataPointer::operator= (o=..., this=0x38471e0) at ././/include/QtCore/qshareddata.h:99 99 ././/include/QtCore/qshareddata.h: Aucun fichier ou dossier de ce type. (gdb) bt #0 0x7630b50e in QSharedDataPointer::operator= (o=..., this=0x38471e0) at ././/include/QtCore/qshareddata.h:99 #1 Digikam::MetaEngineData::operator= (this=0x38471e0, other=...) at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine_data.cpp:51 #2 0x762d72fc in Digikam::DImg::setMetadata (this=, data=...) at /b/dktemp/digikam-master/core/libs/dimg/dimg.cpp:1016 #3 0x76180a91 in Digikam::DImgLoader::readMetadata (this=0x7fff497f9880, filePath=...) at /b/dktemp/digikam-master/core/libs/dimg/loaders/dimgloader.cpp:219 #4 0x7618a10e in Digikam::JPEGLoader::load (this=this@entry=0x7fff497f9880, filePath=..., observer=observer@entry=0x3b0f240) at /b/dktemp/digikam-master/core/libs/dimg/loaders/jpegloader.cpp:92 #5 0x762dfb29 in Digikam::DImg::load (this=this@entry=0x3b0f428, filePath=..., loadFlagsInt=loadFlagsInt@entry=63, observer=observer@entry=0x3b0f240, rawDecodingSettings=...) at /b/dktemp/digikam-master/core/libs/dimg/dimg.cpp:430 #6 0x762e00a0 in Digikam::DImg::load (this=this@entry=0x3b0f428, filePath=..., observer=observer@entry=0x3b0f240, rawDecodingSettings=...) at /b/dktemp/digikam-master/core/libs/dimg/dimg.cpp:374 #7 0x763a353b in Digikam::PreviewLoadingTask::execute (this=0x3b0f230) at /b/dktemp/digikam-master/core/libs/threadimageio/previewtask.cpp:325 #8 0x7638f145 in Digikam::LoadSaveThread::run (this=0x33d7850) at /b/dktemp/digikam-master/core/libs/threadimageio/loadsavethread.cpp:133 #9 0x763d0fce in Digikam::DynamicThread::Private::run (this=0x633fe50) at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:183 #10 0x00347b8aa60f in ?? () from /tmp/.mount_digikasSydoJ/usr/lib/libQt5Core.so.5 #11 0x00347b8ae18a in ?? () from /tmp/.mount_digikasSydoJ/usr/lib/libQt5Core.so.5 #12 0x7570a494 in start_thread (arg=0x7fff497fa700) at pthread_create.c:333 #13 0x7fffed3f8acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #29 from caulier.gil...@gmail.com --- And you let's CM enabled or no ? I recommend to : 1/ test without CM 2/ test with CM + a valid ICC profile 3/ test with CM + a no valid ICC profile. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #28 from Mathieu --- Color Management was effectively activated but no "space color" was selected. I started a maintenance process. I will let you know when it will be finish -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #27 from Maik Qualmann --- Git commit 15f3e3b0645612a8c650cbff58f137f664b287a3 by Maik Qualmann. Committed on 01/09/2018 at 20:05. Pushed by mqualmann into branch 'master'. clear DImg if we have a problem with loading color profile M +1-0core/libs/dimg/filters/icc/iccmanager.cpp https://commits.kde.org/digikam/15f3e3b0645612a8c650cbff58f137f664b287a3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #26 from Maik Qualmann --- It crashes in so many different places, all have almost only in common that it takes place when loading a picture. But by now I think the backtrace is misleading us here. I'm going to make a change to the ICCManager for testing... Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #25 from Mathieu --- I just finish a maintenance process without activating faces detection and it works. So I suppose that the problem is related to this option. I will perform a test with only face detection (single, multicore) and after, I will test your request. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #24 from caulier.gil...@gmail.com --- Maik, Look like with one or more than one core, the result is the same. Mathieu, Did you use the Color Management option ? If yes, can you try again with CM disabled and just one core ? Perhaps something goes wrong with one of your ICC color profile when preview is extracted in maintenance tool. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #23 from Mathieu --- run only with one core... Digikam::DImg::load: "/home/mathieu/Images/Photos/-00-00 - Photos - Famille/foo/2005-08-07_150341 - 80ans BL (001).jpg" : JPEG file identified Digikam::DMetadata::getImageHistory: Loading image history "" Digikam::MetaEngine::getImageDateTime: DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2005-08-07 15:03:41.000 CEST Qt::TimeSpec(LocalTime)) Digikam::MetaEngine::getImageDateTime: DateTime => Exif.Photo.DateTimeDigitized => QDateTime(2005-08-07 15:03:41.000 CEST Qt::TimeSpec(LocalTime)) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile. Digikam::MetaEngine::getImageOrientation: Orientation => Exif.Image.Orientation => 1 Digikam::IccManager::IccManager: Cannot open workspace color profile "/tmp/.mount_digikanbwKZQ/usr/share/digikam/profiles/srgb-d65.icm" Digikam::FaceUtils::writeUnconfirmedResults: Entry QRect(289,567 422x422)603overlapsQRect(289,567 422x422)603, skipping Thread 92 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff45ffb700 (LWP 17366)] 0x in ?? () (gdb) bt #0 0x in ?? () #1 0x7639e7bb in Digikam::LoadingTask::progressInfo (this=0x4bd6350, progress=0.10001) at /b/dktemp/digikam-master/core/libs/threadimageio/loadsavetask.cpp:63 #2 0x7618b57f in Digikam::JPEGLoader::load (this=this@entry=0x7fff45ffa880, filePath=..., observer=observer@entry=0x4bd6360) at /b/dktemp/digikam-master/core/libs/dimg/loaders/jpegloader.cpp:374 #3 0x762dfb29 in Digikam::DImg::load (this=this@entry=0x4bd6548, filePath=..., loadFlagsInt=loadFlagsInt@entry=63, observer=observer@entry=0x4bd6360, rawDecodingSettings=...) at /b/dktemp/digikam-master/core/libs/dimg/dimg.cpp:430 #4 0x762e00a0 in Digikam::DImg::load (this=this@entry=0x4bd6548, filePath=..., observer=observer@entry=0x4bd6360, rawDecodingSettings=...) at /b/dktemp/digikam-master/core/libs/dimg/dimg.cpp:374 #5 0x763a353b in Digikam::PreviewLoadingTask::execute (this=0x4bd6350) at /b/dktemp/digikam-master/core/libs/threadimageio/previewtask.cpp:325 #6 0x7638f145 in Digikam::LoadSaveThread::run (this=0x41badb0) at /b/dktemp/digikam-master/core/libs/threadimageio/loadsavethread.cpp:133 #7 0x763d0fce in Digikam::DynamicThread::Private::run (this=0x6759300) at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:183 #8 0x00347b8aa60f in ?? () from /tmp/.mount_digika4armiY/usr/lib/libQt5Core.so.5 #9 0x00347b8ae18a in ?? () from /tmp/.mount_digika4armiY/usr/lib/libQt5Core.so.5 #10 0x7570a494 in start_thread (arg=0x7fff45ffb700) at pthread_create.c:333 #11 0x7fffed3f8acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #22 from Mathieu --- using version from 31/08/2018 and multi-core option activated Digikam::DMetadata::getImageHistory: Loading image history "" Digikam::MetaEngine::getImageDateTime: DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2004-12-26 10:30:47.000 CET Qt::TimeSpec(LocalTime)) Digikam::MetaEngine::getImageDateTime: DateTime => Exif.Photo.DateTimeDigitized => QDateTime(2004-12-26 10:30:47.000 CET Qt::TimeSpec(LocalTime)) Digikam::FacePipeline::Private::checkFinished: Check for finish: 51 packages, 0 infos to filter, hasFinished() false Digikam::ActionThreadBase::cancel: Cancel Main Thread [Thread 0x7fff28ff9700 (LWP 12859) exited] Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile. Digikam::MetaEngine::getImageOrientation: Orientation => Exif.Image.Orientation => 1 Digikam::IccManager::IccManager: Cannot open workspace color profile "/tmp/.mount_digikanbwKZQ/usr/share/digikam/profiles/srgb-d65.icm" Thread 89 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff2bfff700 (LWP 5815)] 0x in ?? () (gdb) bt #0 0x in ?? () #1 0x76396260 in Digikam::LoadingCache::notifyNewLoadingProcess (this=this@entry=0x831380, process=process@entry=0x50cd900, description=...) at /b/dktemp/digikam-master/core/libs/threadimageio/loadingcache.cpp:243 #2 0x763a34cf in Digikam::PreviewLoadingTask::execute (this=0x50cd730) at /b/dktemp/digikam-master/core/libs/threadimageio/previewtask.cpp:162 #3 0x7638f145 in Digikam::LoadSaveThread::run (this=0x27519e0) at /b/dktemp/digikam-master/core/libs/threadimageio/loadsavethread.cpp:133 #4 0x763d0fce in Digikam::DynamicThread::Private::run (this=0x18a2ea0) at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:183 #5 0x00347b8aa60f in ?? () from /tmp/.mount_digikaz1upX1/usr/lib/libQt5Core.so.5 #6 0x00347b8ae18a in ?? () from /tmp/.mount_digikaz1upX1/usr/lib/libQt5Core.so.5 #7 0x7570a494 in start_thread (arg=0x7fff2bfff700) at pthread_create.c:333 #8 0x7fffed3f8acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 (gdb) I will try without multicore option -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #21 from caulier.gil...@gmail.com --- Maik, Note that the problem is exactly the same in BQM with multi-core support option We have a file in bugzilla to be able to set the core number to use while running BQM. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #20 from Maik Qualmann --- The commit is not the solution and not necessary, I will undo the change again. The problem I suspect actually in no longer existing memory, even if I look at the other backtraces. For 4 CPU cores probably 4GB memory is not enough, because only a lot less will actually be free. Therefore, for testing we will limit the number of CPU cores used to 1 core per 1GB of free memory. So in order to use 8 CPU cores, then 8GB of free memory would have to be available, otherwise the cores used will be gradually reduced. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #19 from caulier.gil...@gmail.com --- In all cases the new appimage will be online and this morning -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #18 from Mathieu --- My laptop is 4 cpus and 4GB memory. Multi-core option was activated during these tests. It won't be possible for me to perform new test today. It will be for Saturday. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #17 from caulier.gil...@gmail.com --- Ok i will build a new AppImage tomorrow morning... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #16 from Maik Qualmann --- Gilles, look into the Commit, I think that was really a mistake. Can you please build new packages so that Mathieu can test it? Yes, Mathieu used all 4 cores. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #15 from Maik Qualmann --- Git commit 67b2bb528b2be26a9a618a4b361440664070ba93 by Maik Qualmann. Committed on 30/08/2018 at 20:39. Pushed by mqualmann into branch 'master'. do not create meta-engine data on the stack but in the heap M +1-1core/libs/dmetadata/metaengine_data.cpp https://commits.kde.org/digikam/67b2bb528b2be26a9a618a4b361440664070ba93 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #14 from caulier.gil...@gmail.com --- I second maik, here. Another Q is : did you use the multi-core option to perform maintenance in parallel ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #13 from Maik Qualmann --- Interesting backtrace. It crashes now in another place. If I look at the backtrace, there is really only an explanation, there is no more memory available. I see from the other post, you have 4 CPU cores. How much memory do you have? Can you if digiKam runs with the maintenance tool, please observe the free memory? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #12 from Mathieu --- Digikam::OpenCVFaceDetector::cascadeResult: detectMultiScale gave () Digikam::DetectionWorker::process: Found 0 faces in "2003-06-28_165437 - 150603 0 (001).jpg" QSize(2048, 1536) QSize(2048, 1536) Digikam::OpenCVFaceDetector::cascadeResult: detectMultiScale: image size 800 600 searchIncrement 1.1 grouping 3 flags 1 min size 26 26 Digikam::FaceUtils::writeUnconfirmedResults: Entry QRect(232,35 84x84)603overlapsQRect(232,35 84x84)603, skipping [New Thread 0x7fff46ffd700 (LWP 10780)] [Thread 0x7fff267fc700 (LWP 10695) exited] Thread 95 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff1dffb700 (LWP 9844)] 0x7630a08e in QSharedDataPointer::operator= (o=..., this=0x812f590) at ././/include/QtCore/qshareddata.h:99 99 ././/include/QtCore/qshareddata.h: Aucun fichier ou dossier de ce type. (gdb) bt #0 0x7630a08e in QSharedDataPointer::operator= (o=..., this=0x812f590) at ././/include/QtCore/qshareddata.h:99 #1 Digikam::MetaEngineData::operator= (this=0x812f590, other=...) at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine_data.cpp:51 #2 0x762d5edc in Digikam::DImg::setMetadata (this=, data=...) at /b/dktemp/digikam-master/core/libs/dimg/dimg.cpp:1016 #3 0x7617f671 in Digikam::DImgLoader::readMetadata (this=0x7fff1dffa880, filePath=...) at /b/dktemp/digikam-master/core/libs/dimg/loaders/dimgloader.cpp:219 #4 0x76188cee in Digikam::JPEGLoader::load (this=this@entry=0x7fff1dffa880, filePath=..., observer=observer@entry=0x813b0b0) at /b/dktemp/digikam-master/core/libs/dimg/loaders/jpegloader.cpp:92 #5 0x762de709 in Digikam::DImg::load (this=this@entry=0x813b298, filePath=..., loadFlagsInt=loadFlagsInt@entry=63, observer=observer@entry=0x813b0b0, rawDecodingSettings=...) at /b/dktemp/digikam-master/core/libs/dimg/dimg.cpp:430 #6 0x762dec80 in Digikam::DImg::load (this=this@entry=0x813b298, filePath=..., observer=observer@entry=0x813b0b0, rawDecodingSettings=...) at /b/dktemp/digikam-master/core/libs/dimg/dimg.cpp:374 #7 0x763a2526 in Digikam::PreviewLoadingTask::execute (this=0x813b0a0) at /b/dktemp/digikam-master/core/libs/threadimageio/previewtask.cpp:325 #8 0x7638dcc5 in Digikam::LoadSaveThread::run (this=0x24a37b0) at /b/dktemp/digikam-master/core/libs/threadimageio/loadsavethread.cpp:133 #9 0x763cfc0e in Digikam::DynamicThread::Private::run (this=0x4350d40) at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:183 #10 0x00347b8aa60f in ?? () from /tmp/.mount_digika6ykiGm/usr/lib/libQt5Core.so.5 #11 0x00347b8ae18a in ?? () from /tmp/.mount_digika6ykiGm/usr/lib/libQt5Core.so.5 #12 0x75706494 in start_thread (arg=0x7fff1dffb700) at pthread_create.c:333 #13 0x7fffed3f4acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #11 from Mathieu --- Sorry for the mistake. I'll perform the test with the last version and come back to you -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #10 from Maik Qualmann --- The version you tested is from 17.08.2018. Please test it with the current version from 29.08.2018. Available at https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #9 from Mathieu --- test with digikam-6.0.0-git-20180817T182155-x86-64.appimage Digikam::MaintenanceMngr::setSettings: wholeAlbums : true wholeTags : true Albums: 1073 Tags : 557 useMutiCoreCPU: true newItems : true thumbnails: true scanThumbs: true fingerPrints : true scanFingerPrints : true duplicates: false minSimilarity : 90 maxSimilarity : 100 duplicatesRestriction : 0 faceManagement: true faceScannedHandling : 1 qualitySort : false quality : EnableSorter : true DetectBlur: true DetectNoise : true DetectCompression : true DetectOverexposure :true LowQRejected : true MediumQPending: true HighQAccepted : true Speed : 1 Rejected Threshold: 10 Pending Threshold : 40 Accepted Threshold: 60 Blur Weight : 100 Noise Weight : 100 Compression Weight: 100 qualityScanMode : 1 metadataSync : true syncDirection : 0 databaseCleanup : true cleanThumbDb : true cleanFacesDb : true shrinkDatabases : true Digikam::MaintenanceMngr::stage1: stage1 Digikam::NewItemsFinder::slotStart: scan mode: CompleteCollectionScan [Thread 0x7ffeeb7fe700 (LWP 10042) exited] Digikam::NewItemsFinder::slotTotalFilesToScan: total scan value : 68646 Digikam::CollectionScanner::completeHistoryScanning: items to tag () Digikam::CollectionScanner::completeScan: Complete scan took: 17432 msecs. Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using 4 CPU core to run threads [New Thread 0x7ffeeb7fe700 (LWP 10533)] Digikam::ActionThreadBase::run: Action Thread run 1 new jobs [New Thread 0x7ffeebfff700 (LWP 10534)] Digikam::ImageQueryBuilder::buildQueryFromXml: " ( ( (ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM TagsTree WHERE pid=?)) AND ImageTagProperties.property=? ) OR ( (ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM TagsTree WHERE pid=?)) AND ImageTagProperties.property=? ) OR ( (ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM TagsTree WHERE pid=?)) AND ImageTagProperties.property=? ) ) " Digikam::ImageLister::listImageTagPropertySearch: Search query: "SELECT DISTINCT Images.id, Images.name, Images.album, Albums.albumRoot,ImageInformation.rating, Images.category, ImageInformation.format, ImageInformation.creationDate, Images.modificationDate, Images.fileSize,ImageInformation.width, ImageInformation.height,ImageTagProperties.value, ImageTagProperties.property, ImageTagProperties.tagid FROM ImagesINNER JOIN ImageTagProperties ON ImageTagProperties.imageid=Images.idLEFT JOIN ImageInformation ON Images.id=ImageInformation.imageidINNER JOIN Albums ON Albums.id=Images.album WHERE Images.status=1 AND ( ( ( (ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM TagsTree WHERE pid=?)) AND ImageTagProperties.property=? ) OR ( (ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM TagsTree WHERE pid=?)) AND ImageTagProperties.property=? ) OR ( (ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM TagsTree WHERE pid=?)) AND ImageTagProperties.property=? ) ) );" (QVariant(int, 603), QVariant(int, 603), QVariant(QString, "autodetectedPerson"), QVariant(int, 603), QVariant(int, 603), QVariant(QString, "autodetectedFace"), QVariant(int, 603), QVariant(int, 603), QVariant(QString, "tagRegion")) Digikam::NewItemsFinder::slotTotalFilesToScan: total scan value : 68646 Digikam::ImageLister::listImageTagPropertySearch: Search result: 16503 Digikam::ActionThreadBase::cancel: Cancel Main Thread [Thread 0x7ffeeb7fe700 (LWP 10533) exited] [New Thread 0x7ffeeb7fe700 (LWP 10539)] Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 0 Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::ActionThreadBase::cancel: Cancel Main Thread [Thread 0x7ffeebfff700 (LWP 10534) exited] Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 250 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 500 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 750 Digikam::CollectionScanner::completeHistoryScanning: items to tag () Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 1000 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 1250 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 1500 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 1750 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 caulier.gil...@gmail.com changed: What|Removed |Added Platform|Debian stable |Appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #8 from Mathieu --- -rw-r--r--. 1 root root 6924 août 17 18:28 srgb-d65.icm -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #7 from caulier.gil...@gmail.com --- As expected... So the question is : why this file cannot be loaded as we can see in the debug trace from the console. What's the properties of this ICC profile from the bundle with ls -al ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #6 from Mathieu --- Yes, srgb-d65.icm exists in this folder -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #5 from caulier.gil...@gmail.com --- Mathieu, Look the message : Digikam::IccManager::IccManager: Cannot open workspace color profile "/tmp/.mount_digikanbwKZQ/usr/share/digikam/profiles/srgb-d65.icm" This file must be included in the AppImage bundle. At run time, AppImage is decompressed in memory and monted to a temporary dir. This one change at each session. On your trace : /tmp/.mount_digikanbwKZQ/ is the temporary dir. The dir name is always mounted to /tmp and named with the prefix .mount_digika, the rest is change. It's easy to found new one used at a new session. Just list dir starting with ".mount_digika" in /tmp. It must have only one. So, my question is : do you see the "usr/share/digikam/profiles/srgb-d65.icm" file in the temporary directory ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #4 from Maik Qualmann --- Git commit 50b066772cc02a2c9de39fb9676df8fad30ec146 by Maik Qualmann. Committed on 28/08/2018 at 06:06. Pushed by mqualmann into branch 'master'. postprocessing only with valid image M +6-1core/libs/threadimageio/loadsavetask.cpp https://commits.kde.org/digikam/50b066772cc02a2c9de39fb9676df8fad30ec146 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #3 from Mathieu --- (gdb) bt #0 0x7fffe8b8df78 in main_arena () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x763d6ec8 in Digikam::SharedLoadingTask::postProcess (this=0x83768f0) at /b/dktemp/digikam-master/core/libs/threadimageio/loadsavetask.cpp:335 #2 0x763da442 in Digikam::PreviewLoadingTask::execute (this=0x83768f0) at /b/dktemp/digikam-master/core/libs/threadimageio/previewtask.cpp:399 #3 0x763c6605 in Digikam::LoadSaveThread::run (this=0x866530) at /b/dktemp/digikam-master/core/libs/threadimageio/loadsavethread.cpp:133 #4 0x7640838e in Digikam::DynamicThread::Private::run (this=0x672c9c0) at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:183 #5 0x7fffea4bb60f in ?? () from /tmp/.mount_digikaedpRtT/usr/lib/libQt5Core.so.5 #6 0x7fffea4bf18a in ?? () from /tmp/.mount_digikaedpRtT/usr/lib/libQt5Core.so.5 #7 0x7536a494 in start_thread (arg=0x7ffeef7fe700) at pthread_create.c:333 #8 0x7fffe88dcacf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #2 from Mathieu --- Digikam::DImg::load: "/home/mathieu/Images/Photos/-00-00 - Photos - Famille/foo/2005-08-07_170334 - DSC01571 (001).JPG" : JPEG file identified Digikam::DMetadata::getImageHistory: Loading image history "" Digikam::MetaEngine::getImageDateTime: DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2005-08-07 17:03:34.000 CEST Qt::TimeSpec(LocalTime)) Digikam::MetaEngine::getImageDateTime: DateTime => Exif.Photo.DateTimeDigitized => QDateTime(2005-08-07 17:03:34.000 CEST Qt::TimeSpec(LocalTime)) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile. Digikam::MetaEngine::getImageOrientation: Orientation => Exif.Image.Orientation => 1 Digikam::IccManager::IccManager: Cannot open workspace color profile "/tmp/.mount_digikanbwKZQ/usr/share/digikam/profiles/srgb-d65.icm" Digikam::FaceUtils::writeUnconfirmedResults: Entry QRect(794,590 191x191)53overlapsQRect(797,590 191x191)603, skipping Digikam::DImg::copy: : return null image! ( false , 0 , 0 ) Digikam::FaceUtils::writeUnconfirmedResults: Entry QRect(1393,761 253x254)603overlapsQRect(1393,761 253x254)603, skipping Digikam::FaceUtils::writeUnconfirmedResults: Entry QRect(809,220 189x190)38overlapsQRect(809,223 187x187)603, skipping Digikam::FaceUtils::writeUnconfirmedResults: Entry QRect(1224,256 172x172)603overlapsQRect(1224,256 172x172)603, skipping Digikam::DImg::copy: : return null image! ( false , 0 , 0 ) Digikam::FaceUtils::writeUnconfirmedResults: Entry QRect(1085,807 125x125)603overlapsQRect(1085,807 125x125)603, skipping Digikam::FaceUtils::writeUnconfirmedResults: Entry QRect(891,310 115x115)38overlapsQRect(888,307 120x120)603, skipping Digikam::DImg::copy: : return null image! ( false , 0 , 0 ) [New Thread 0x7fff2affd700 (LWP 32060)] [Thread 0x7fff2affd700 (LWP 31962) exited] [Thread 0x7fff4ab6d700 (LWP 32049) exited] Thread 611 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffeef7fe700 (LWP 28287)] 0x7fffe8b8df78 in main_arena () from /lib/x86_64-linux-gnu/libc.so.6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- It sound like a crash in face engine, but not sure. We need a GDB backtrace. You can run the AppImage bundle in GDB with the "debug" option to pass on command line. Look here for details : https://files.kde.org/digikam/README Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
