https://bugs.kde.org/show_bug.cgi?id=392133
--- Comment #39 from PhobosK <phob...@fastmail.fm> --- Created attachment 141297 --> https://bugs.kde.org/attachment.cgi?id=141297&action=edit heaptrack.krusader.jpg I found something very strange about this memory hog.... It still happens on my system - right after krusader is started it has some 20-30 sec delay before its window is painted, the next 10 min it gets >200 Mb mem usage and for an hour it ups to 1.5 Gb. I found that there is mem leaking connected to KDirWatch, started by KBookmarkManager. The truth is I have around 50 bookmarks from diff protocols - sftp:/, file:/, smb:/ - and some of them were old with missing paths. So I decided to leave only those working - ~20 - but it didn't help. I turned off the search in bookmarks too - but it didn't help either. Krusader from my root profile with only 5 bookmarks with the file:/ protocol doesn't have this memory problem + it starts (paints) the window almost immediately after the start and memory usage stays at max 30 Mb for a long time.... I am sorry that I attach a screenshot only of heaptrack, but this is taken on the 15 min of usage of krusader and is sorted by "Leaked" memory. The system is: Krusader 2.7.2 KDE Frameworks 5.85.0 KDE Apps 21.08.1 Qt 5.15.2 The xcb windowing system I do not know if it is relevant (I think KDirWatch is also dependent on it) but because of baloo and idea I have set: fs.inotify.max_user_watches = 524288 I hope this will help Thanks -- You are receiving this mail because: You are watching all bug changes.
