https://bugs.kde.org/show_bug.cgi?id=381877
--- Comment #27 from caulier.gil...@gmail.com --- Ok, now we will investiguate the memory leak with valgrind. Start digiKam from a console like this : valgrind --tool=memcheck --leak-check=full --error-limit=no digikam This will run DK in Valgrind which will catch the memory corruptions. This slow down digiKam. Just report here all the trace from the console until the end of digiKam session. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
