https://bugs.kde.org/show_bug.cgi?id=398908
--- Comment #103 from Knut Hildebrandt <knut.hildebra...@gmx.de> --- Back with a short summery of my observations. 1. with the moment of its start a dolphin instance begins to constantly allocate memory 2. the amount of memory allocated as well as the CPU time used correlates with the number of tabs and views open and grows over time 3. the memory allocation does not depend on user interaction. Opening files several GB big does not cause any jump in memory usage. On the other hand the memory usage increases constantly even without any user interaction at all. 4. hibernating the machine brings the used memory down to about 20 to 30 MB for each instance, but within minutes, sometimes seconds, it is back to the level before hibernation and than further rising 5. over time and with many dolphins, tabs and views open not only the dolphin instances get very slow but the machine too, due to constant swapping For me there arise a few questions: 1. why does dolphin constantly allocate memory even though there is no user interaction? 2. what does dolphin need the saved data for, since it obviously works well with memory usage far below 100 MB even if there are many tabs open? 3. Why once allocated memory never gets freed? All the data I mention here I gathered in KSysGuard. I've no idea what tools I have to use to collect more useful data. One last thing. The original title of the bug report was something like "Dolphin uses huge amounts of memory" and has been changed since a potential memory leak has been identified. Since this bug was fixed the bug report has been closed even though the problem I reported three years ago still exists. Thus I'd propose to reopen the bug and change it's title back to the original one. -- You are receiving this mail because: You are watching all bug changes.
