[digiKam-users] Digikam 6.2 beta memory leaks?

Gilles Caulier caulier.gilles at gmail.com
Wed May 8 18:17:08 BST 2019


Here a quick test on my host computer, to rebuild all finger prints
indicate a memory allocation moving from 800Mb to 1.6Mb, depending of
the operations done in background (visible on the console). The memory
is allocated and free when transactions is complete to the database
(here Mysql). The memory graph provided by the desktop (Plasma) do not
indicate a huge memory leak. The fluctuations exists but it's
negligible. Here the collection is huge and the computation take age.
Image to register are JPEG, PNG, TIFF, and RAW.

So, typically, it's not reproducible here.

Gilles Caulier

Le mer. 8 mai 2019 à 19:09, Gilles Caulier <caulier.gilles at gmail.com> a écrit :
> Hi,
> There is no special changes done in Fingerprints processing.
> The main changes in whole source code in 2 ports to C++11
> compatibility ; nullprt and virtual overide. Both change code
> everywhere.
> How did you investiguate the memory leak exactly ? With valgrind or
> just to check the memory consumption through the linux kernel stats ?
> Did you compile yourself whole code, or did you try the AppImage linux bundle ?
> Best
> Gilles Caulier
> Le mer. 8 mai 2019 à 19:04, <leoutation at gmx.fr> a écrit :
> >
> > Hi
> > I had to downgrade from digikam-git 6.2 beta to digikam 6.1 because 6.2
> > eats huge memory, about 4 Go when rebuilding fingerprints (18.000
> > images). No dk error when launching it in console.
> > This dk version is unusable for me. Worth thing is computer freezing. I
> > had to kill user/digikam process in tty console.
> > Mysql eats only 200M.
> > A digikam memory leaks?
> > Mysql external db on local hard drive.
> > Archlinux system
> >
> > --
> > Maderios

More information about the Digikam-users mailing list