https://bugs.kde.org/show_bug.cgi?id=492808
--- Comment #5 from tagwer...@innerjoin.org --- (In reply to Ellie from comment #4) > ... postmarketOS Edge ... It uses OpenRC ... My apologies, I missed the line in your summary. I'm not sure whether that gives you the same functionality (of limiting the use of resources by setting up cgroups). On systemd based systems, Baloo is limited in the amount of memory it can "grab" though a unit file, you can say it should not use more than 25% of RAM and never swap. That's the 'backstop" protection, the OS prevents the process taking more... It would still be worth running "balooctl monitor", that ought to give you the stream of filenames as Baloo indexes them. It's possible that you'll see a pattern. Things like a log file being indexed over and over again... or Baloo gradually working its way though a massive Maildir folder or stuck indexing a gigabyte .mbox file -- You are receiving this mail because: You are watching all bug changes.
