https://bugs.kde.org/show_bug.cgi?id=380456
--- Comment #18 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- (In reply to tagwerk19 from comment #17) > If you look at htop, you'll see that baloo_file and baloo_file_extractor run > with minimum priority. They'll yield to nearly everything that wants a CPU. > They should take all the time they need without annoying anything else.... Hmm, even assuming this is true, does the process suspend if the user is on battery? An otherwise idle system consuming 100% of a core for hours on end is sure to annoy the user even if it doesn't interfere with other processes. I'd also point out that I discovered this issue (after several years of being vaguely aware of "baloo problems") when I saw stuttering in a full screen game. Alt-tabbing to htop showed baloo_file_extractor at 100%. Baloo may in theory yield to other processes, but it didn't prevent me from seeing issues. > Memory usage is different, baloo "memory maps" the index and pulls pages > from disc to memory as needed, they'll be "forgotten" again if the RAM is > needed (and the pages have not been modified). You might see that baloo_file > / baloo_file_extractor use a lot of memory but that can be "just cache". If I'm not mistaken, that's just for internal Baloo memory usage, right? In my case, baloo_file_extractor is calling out to an external library (poppler), and that library is consuming an endlessly growing amount of memory (from 1-3 GB before I've killed it). It's probably safe to say that this memory usage is in the form of anonymous mappings which can't be reclaimed. Baloo *must* take that into account and kill the extractor process if it begins affecting system resources. > I'm tempted to say that if this is a application generated file with > little/no human readable information in it (that happens to be a PDF) it > would make sense to have an application specific mimetype for it. Then that > can be added to baloo's "exclude filters" list. I suspect though that if the > file is generated by a script, that might not be possible. In this case, it's a graph of some scientific data. Plotting scientific data to PDF or SVG (which both can have extractable text) is very common. In any case, it shouldn't be on the user to determine which files are causing problems (I had to use strace!) and exclude them. A file indexer should "just work". -- You are receiving this mail because: You are watching all bug changes.
