https://bugs.kde.org/show_bug.cgi?id=398908
--- Comment #40 from Andreas Kilgus <k...@fuenfsieben.de> --- (In reply to David Hallas from comment #38) > I am still trying to reproduce this locally, and lately I have been using > the excellent Heaptrack > (https://milianw.de/blog/heaptrack-a-heap-memory-profiler-for-linux.html) > tool to look at Dolphins memory usage, but I still haven't been able to > pinpoint any code that keeps consuming memory. The tool reports some minor > leaks, but they all appear to be one-off allocations, so they shouldn't > cause the heap to grow over time. I was thinking if it would be possible for > one of you who is able to reproduce the problem to use the tool to dump what > is using memory and share the results here? One of my dolphin instances was running under surveillance of heaptrack for almost an hour. I changed directories, enabled/disabled previews, hibernated once, used the search form, let display context menues, copied one file (155 MiB) in split view, deleted the file afterwards and closed one of the views. Dolphin started with ~40 MiB, current memory consumption is ~181 MiB. Heaptracks compressed protocol ist about ~63 MiB. I'm not sure if I'm willing to share the protocol in public since it might contain confidential data (I haven't learned the whatabouts of heaptrack in detail). What kind of result(s) do you want me to share to help your debugging efforts? -- You are receiving this mail because: You are watching all bug changes.
