https://bugs.kde.org/show_bug.cgi?id=437197
--- Comment #9 from Ian Proudler <i.proud...@oxon.org> --- (In reply to tagwerk19 from comment #6) > Here's another guess, maybe worth mentioning... > > You are doing content indexing - and indexing a lot of data? How big has > your .local/share/baloo/index file become? What does > > balooctl indexSize > > say? It could be that baloo is wanting more bits of the database in memory > than there is memory available. In that case there'll be lots of going back > and forth to disc. Having a look at your system load (memory, swap) might > give some clues Just in case it helped, I decided to 'purge' the index. I'm happy to report that so far, baloo is is indexing files and contents without any obvious impact on my system. So perhaps there was something wrong with my index file. The last time I reset it was some years ago. -- You are receiving this mail because: You are watching all bug changes.
