https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #26 from caulier.gil...@gmail.com --- Marcel, If there is a memory leak somewhere with your Linux box (i see nothing with mine) valgrind can certainly help to identify the dirty code. Look here to see how to run digiKam in valgrind (running speed is decreased by 20). https://www.digikam.org/api/index.html#memleak I full valgrind console trace can be instructive as the memory leak can be located outside digiKam... Gilles -- You are receiving this mail because: You are watching all bug changes.
