https://bugs.kde.org/show_bug.cgi?id=440802
--- Comment #1 from [email protected] --- (In reply to irchaika from comment #0) > It consumes nearly a gigabyte of ram despite being idle, the problem > persists across reboots (though I haven't checked how long it takes for the > process to reappear and take that amount of ram) I've seen this when I've tried indexing many files (2 million), that gives a big index. Each time you log on, baloo cross-checks your files on disc against the files in the index to see if anything has changed. In this case baloo is just reading most of the information, it gets pulled off disc and stays in RAM in case it is needed again. If "balooctl status" says idle, then baloo is not actively using the memory, I would expect that as soon as another process needs memory, the amount used by baloo will drop. -- You are receiving this mail because: You are watching all bug changes.
