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
https://bugs.kde.org/show_bug.cgi?id=397919
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Version Fixed In|
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://fi
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.
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.
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.
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
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-3c
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 +2
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 -1co
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
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 -1c
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 39
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 re
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"
Re
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: bu
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 l
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.
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 ca
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 beca
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 bu
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
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 ICCManage
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,
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 someth
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
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(20
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 receivin
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 memo
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.
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
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.
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 ar
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
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.
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
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::OpenCVFaceDe
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.
https://bugs.kde.org/show_bug.cgi?id=397919
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #10 from Maik
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
useM
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 m
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.
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 Cauli
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.
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 AppI
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/threa
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/threadimag
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::M
https://bugs.kde.org/show_bug.cgi?id=397919
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
49 matches
Mail list logo
