https://bugs.kde.org/show_bug.cgi?id=398908
--- Comment #38 from David Hallas <da...@davidhallas.dk> --- 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? This page has details and how to clone, build, install and run it: https://milianw.de/blog/heaptrack-a-heap-memory-profiler-for-linux.html -- You are receiving this mail because: You are watching all bug changes.
