https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #37 from caulier.gil...@gmail.com --- Marcel, Looking your full valgrind trace do not show any memory leak, only uninitialized values. As explain here : https://stackoverflow.com/questions/2612447/pinpointing-conditional-jump-or-move-depends-on-uninitialized-values-valgrin This can be considerate as false positive and in all cases not the real case of the leak of memory from face detection. How to investigate better : 1/ always use a digiKam compiled with debug symbols using valgrind. 2/ The whole memory leak trace is generally reported at end of valgrind session, when digiKam is down. Valgrind will take time to list leak sorted by size. This part of valgrind report is missing in your trace. Gilles -- You are receiving this mail because: You are watching all bug changes.
