https://bugs.kde.org/show_bug.cgi?id=380456
--- Comment #19 from tagwer...@innerjoin.org --- (In reply to Adam Fontenot from comment #18) > 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'm pretty confident about the CPU priority and I know that baloo is aware that it is on battery (and avoids content indexing). What happens in your case, I'm afraid I don't know. > 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. I would still suspect memory use rather than CPU as the underlying reason. There are situations where baloo is building a large transaction and requires lots of memory, there's a summary starting https://bugs.kde.org/show_bug.cgi?id=400704#c31. It's quite possible for systems to "hit the mud" in these cases. > If I'm not mistaken, that's just for internal Baloo memory usage, right? I'd say yes, the cases I've looked at were when indexing large text files and writing the results to the index. > ... 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. That's a *lot* of memory for a "pdf to text" conversion 8-] You see the baloo_file_extractor RAM usage go up during the extraction and not come down when it is finished? > 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. Understood. Could you see the culprit file in "System Settings > Search" (recent releases of baloo show the progress of the indexing there) or when running "balooctl monitor"? In your use case, you could save your plots to a folder that was not indexed. Yes, I know, it's shouldn't be up to the user but in this case as a workround... > A file indexer should "just work". Yup, I think there's general agreement on that :-) -- You are receiving this mail because: You are watching all bug changes.
