[frameworks-kio] [Bug 398908] Dolphin uses up huge amounts of memory over time

[Méven Car]

https://bugs.kde.org/show_bug.cgi?id=398908

Méven Car <meven29 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |meven29 at gmail.com

--- Comment #106 from Méven Car <meven29 at gmail.com> ---
(In reply to Knut Hildebrandt from comment #103)
> 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.

valgrind would be nice to use to check for memory leak.
`valgrind dolphin` would suffice to learn a

Does closing tabs or views release memory?

To some extent dolphin will always use more memories for each tab and views,
since each need an independent KCoreDirLister, that is a cache to read and
access the filesystem and enrich the data, and those will use proportionally
memory as the directory they access are big.
We still have room for optimization for sure.

-- 
You are receiving this mail because:
You are on the CC list for the bug.