https://bugs.kde.org/show_bug.cgi?id=381877
--- Comment #15 from caulier.gil...@gmail.com --- Ok, now it's clear. Next stage is to discovering Which king of file create this memory dysfunction on your computer. Remember that it's not reproducible here. Can you imagine this kind of dysfunction for an application running in production this is not acceptable. So typically, digiKam allocate the memory when it's scan the collection of image. Can you confirm ? There is no other operation running in background. Right ? If yes, use the digiKam appimage, as explained previously in this thread, but with another account on your system. Typically, a fresh account where you will import step by step the albums from your collection, to discover which kind of files mangle the memory. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.