https://bugs.kde.org/show_bug.cgi?id=380456
--- Comment #15 from DDR <robertsdavid...@gmail.com> --- I second this. It's a bit absurd to just run it with no resource limits, internally or externally. On Wed., Oct. 13, 2021, 11:04 p.m. Adam Fontenot, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=380456 > > Adam Fontenot <adam.m.fontenot+...@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| > |adam.m.fontenot+kde@gmail.c > | |om > > --- Comment #14 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- > This is still a really common issue. I don't know that I've ever spoken to > someone who uses KDE + Baloo with the out of the box settings who hasn't > run > into it. I mean, just for a starting sample: > > > https://old.reddit.com/r/kde/comments/j77j16/can_we_please_have_kde_disable_baloo_by_default/ > > https://old.reddit.com/r/kde/comments/kzdoux/baloo_should_be_suspended_when_the_system_is_in/ > https://old.reddit.com/r/kde/comments/lgg0su/how_is_baloo_doing_these_days/ > https://old.reddit.com/r/kde/comments/o6w0ly/whats_wrong_with_baloo/ > > https://old.reddit.com/r/kde/comments/pc4wk1/baloo_file_extr_extreme_cpu_usage/ > > This is just the first five issues I could find with people talking about > this > *exact* problem, but the list goes on and on. The oldest complaint in that > list > is only a year old. > > More than a complaint, I have a proposal: it is completely unreasonable > for a > file indexer to ever make a user's system unusable. Any time it takes > baloo_file_extractor more than 30 seconds to pull the text out of a file, > or it > starts using more than 10% of the user's total RAM, it should be instantly > killed and the file blacklisted. Only the file name (not contents) should > be > available to search results. > > Moreover, some kind of heuristic is desperately needed to tell Baloo that a > file can't be usefully indexed. Baloo is happy to use a ton of memory and > hard > disk space to index files that are - for most purposes - random binary > data. > > Just as an example: I have a PDF that contains no meaningful text at all > (it's > a plot automatically generated from some technical data). It's only 20 MB. > Yet > baloo_file_extractor hung on this file for a *long* time, probably more > than > half an hour, with RAM use up over 1 GB. It continued using 100% of one CPU > core despite the fact that I was trying to run a full screen game at the > time. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
