https://bugs.kde.org/show_bug.cgi?id=464318
caulier.gil...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |caulier.gil...@gmail.com
--- Comment #2 from caulier.gil...@gmail.com ---
Mine is also on a NVME 1Tb ssd. Size of collections is around 550Mb. Computer
is an i7 with 32Gb and NVidia video card.
Scanning whole collection from scratch take around 1 hour. No crash. I tried
with 7 and 8 digiKam versions, there is no difference. Database is sqlite.
Memory allocated is stable around 2Gb, no more.
System is Kubuntu 22.04 LTS.
Which OpenCV version did you use. Please copy the whole contents of
Help/Components Info dialog. There are plenty of *GPU* API calls in valgrind.
We do not use it in digiKam code, but OpenCV certainly. In last OpenCV 4.7.0,
memory leaks have been reported.
When application crash, please capture a gdb backtrace. See instructions here :
https://www.digikam.org/contribute/
Also i recommend to test the AppImage Linux bundle that we provide, where all
GPU usages are disabled in OpenCV (at compilation time).
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
