https://bugs.kde.org/show_bug.cgi?id=380456
--- Comment #25 from tagwer...@innerjoin.org --- (In reply to Adam Fontenot from comment #24) > ... The limit set on the kde-baloo service is unmodified from the default (512 > MB), so presumably enabling Baloo from the terminal has somehow bypassed the > systemd service that is supposed to control it. That seems like a bug that > should probably be fixed (but the memory leak is an issue regardless) ... A "balooctl enable" doesn't start the service through systemd so escapes the memory limits, noted in Bug 488178. That needs a bit of love... Possible that baloo_file was killed OOM, there might be hints in the journal. I tend towards a MemoryHigh limit of 25% rather than 512M. However, if you got past the https://ipfs.io/ipfs/QmVqWhPuQkE7reTN5F9TiSeA75z62VNaZUSFZz3FdWTLbC PDF, then that's a small success... > ... If there is a way to debug the index and > see which files are using the most space I would love to provide more > details, and this would allow me to selectively exclude certain directories > as well ... That's a good question. No, I've no idea whether that's possible. That sort of detail is hidden in the LMDB library... > I'm returning this issue to "reported" because of the memory problem in (3). Fine! -- You are receiving this mail because: You are watching all bug changes.
