While monitoring baloo process using balooctl and after deleting a folder with big tree depth baloo process starts to consume memory and it never liberates it, then it create huge index. See bellow video link for more info. https://vimeo.com/674181027 Operating System: Manjaro Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.4.173-1-MANJARO (64-bit) Graphics Platform: X11
Is Bug 437754 the same? The dangerous bit is doing the "balooctl status". My guess is you are reading at the same time as the individual deletes want to write. The writes are then done as appends and the index baloons in size...
(In reply to tagwerk19 from comment #1) > Is Bug 437754 the same? > > The dangerous bit is doing the "balooctl status". My guess is you are > reading at the same time as the individual deletes want to write. The writes > are then done as appends and the index baloons in size... Yeah you are right, I think the same problem. This component holds the rank of second broken app in KDE after Akonadi. I don't know if any alternative can replace it or it should be rewritten from scratch. *** This bug has been marked as a duplicate of bug 437754 ***