[Digikam-users] Digikam memory usage

Alberto Ferrante alberto.ferrante at tiscali.it
Mon Nov 14 22:38:54 GMT 2011

Dear Gilles,
attached to this message you can find the log. As you can see at the end
the program was terminated after having filled all the available memory
(20GB!) after having read 4'600 jpgs. The "invalid read" you see in the
report are generated at the beginning of the execution, before starting
to import a collection.

I do not think that one solution would be to divide the processing of
data in "chunks": the program should not wait at the end of the scan to
do all the processing, it should do it after it read X (100?) files.


> In first, we must identify where memory is lost.
> Run digiKam through valgrind from a console, an report the trace here.
> For details, look here :
> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/HACKING#L281
> Gilles Caulier

Home page: http://www.alari.ch/people/alberto
Photo galleries : http://albertoferrante.name
Public key: http://www.alari.ch/people/alberto/keys/yahoo.asc
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: digikam.log
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20111114/8ffcc2b0/attachment.ksh>

More information about the Digikam-users mailing list