https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #1 from Jens ---
Update: this also happens when using the other engine (not the deep learning
engine), and the memory usage stays at >1GB after using face detection, and
memory usage was <200MB before using face detection.
So there is a lea
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #2 from Jens ---
Update 2: With appimage 20181208, memory usage also spikes, but not as high (up
to ~900MB, instead of 1.5GB). Same database, same settings, etc.
Also, with both engines, the speed for detection has become RREEAALLYY SSLLOOW
https://bugs.kde.org/show_bug.cgi?id=402320
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #4 from Jens ---
Main dialog:
- select "search again and merge results" in dropdown menu
- select "detect and recognize faces"
Options:
- Albums: choose some albums (in my case, 10..56)
- all keywords (default)
- Parameters: 80% precision
-
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #5 from Jens ---
I am now using the appimage from 20181228 and the memory hole has even become
worse. The digikam process now has 2GB resident memory without using face
detection at all, just for having Digikam hang around in the background
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #6 from Jens ---
I should add I am using Digikam on a dual screen setup, one 1920x1080 FullHD
monitor and one 2560x1440 QHD-Monitor to the left (secondary screen).
Just in case this makes a difference ...
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #7 from caulier.gil...@gmail.com ---
Well i use also, dual screen, and i cannot reproduce the memory consomption in
all case.
2 gb is enormous and i use system indicators if a whole memory leak appears
while debugging.
Which host system do
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #8 from Jens ---
KDE Neon (based on Ubuntu 18.04) with all updates applied. 64bit.
I have about 180GB of images and videos, ~33000 files.
If you want we can debug this together, using Teamviewer or something.
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=402320
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #9 from Maik
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #10 from Jens ---
Basically, this started after Linux's OOM killer went on a rampage on my system
a few times. I have 8GB of RAM. After the initial shock I started looking more
closely and it *always* happened when digikam had been running f
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #11 from Jens ---
Anything I can enable using kdebugdialog5 to help track this?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #12 from caulier.gil...@gmail.com ---
I suspect something about OpenGL and video card driver.
Why ? because Face management is relevant of OpenCV library which is... a big
puzzle.
I know already that OpenCL feature in OpenCV is problematic a
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #13 from Jens ---
Will do.
For now, I cleaned all databases, started Digikam (~160MB RSS), then looked at
a single image (preview) and RSS went up to ~312MB. Just because of a single
image. Look at another one, RSS jumps to 512MB. Very stra
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #14 from Maik Qualmann ---
The memory increases when looking at images is normal. We perform preloading,
the next images are already loaded into a QCache. The memory error message from
Exiv2 is rather strange.
Maik
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #15 from Maik Qualmann ---
Can you provide an image that triggers the "invalid memory allocation request"?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #16 from caulier.gil...@gmail.com ---
Yes, this is very strange than non of previewer cannot load a JPG thumbnail...
it's it ?
libjpeg, Exiv2, ffmpeg, qimage. none can load the image contents to render a
small preview.
This is definitively
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #17 from Jens ---
20180930_161217.jpg is indeed broken - no thumbnail and no preview. I actually
didn't notice that at all. So this image is probably not part of the problem.
I installed Virtualbox, KDE Neon 18.04 and Digikam appimage and s
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #18 from caulier.gil...@gmail.com ---
No. 6.0.0 database include new tables which are incompatible with 5.9.0.
Try the same test with a fresh database and 5.9.0.
Gilles
--
You are receiving this mail because:
You are watching all bug chan
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #19 from Jens ---
5.9 on new user account with clean KDE Neon installation:
- after first startup, 370MB - more than 6.0-beta3, actually
- after previewing images: 376MB, 400MB, ... up to 531MB
- after detecting faces: 514MB
Don't get me wr
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #21 from caulier.gil...@gmail.com ---
Jens,
I found this opencv topic to disable opencl (GPU) usage with opencv at runtime.
https://github.com/opencv/opencv/issues/9852
Typically, there is an env.variable to setup before to run digikam :
https://bugs.kde.org/show_bug.cgi?id=402320
--- Comment #20 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=402320
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||7.0.0
Status|REPORTED
22 matches
Mail list logo
