Bug 449713

Summary:	balooctl suffers from leak memory and create huge index after deleting a folder
Product:	[Frameworks and Libraries] frameworks-baloo	Reporter:	medin <med.medin.2014>
Component:	balooctl	Assignee:	baloo-bugs-null
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	tagwerk19
Priority:	NOR
Version First Reported In:	5.90.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description medin 2022-02-06 18:48:55 UTC

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

Comment 1 tagwerk19 2022-02-06 21:33:05 UTC

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...

Comment 2 medin 2022-02-06 23:18:54 UTC

(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 ***