Bug 331936

Summary:	akonadi_baloo_indexer RAM usage is too high while indexing mails
Product:	[Unmaintained] Baloo	Reporter:	Romário Rios <luizromario>
Component:	General	Assignee:	Vishesh Handa <me>
Status:	RESOLVED FIXED
Severity:	major	CC:	andre.vmatos, arthur, hrvoje.senjan, thomas.bigot
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Romário Rios 2014-03-10 02:26:48 UTC

Right after I made the migration from Nepomuk to Baloo and Kontact started, the akonadi_baloo_indexer RAM consumption was increasing pretty quickly while it was indexing my mail and it kept increasing up to 2.2 GiB until I killed the process. Then it started again and the RAM consumption only stopped (at 1.4 GiB) increasing after it stopped indexing my mail.

Running KDE SC 4.13 Beta 1.

Reproducible: Always

Comment 1 Romário Rios 2014-03-16 12:17:35 UTC

Bug still present in Beta 2.

Comment 2 Vishesh Handa 2014-03-21 16:46:34 UTC

Please test out beta3 and see if this is still a problem. I'm leaving the bug open for now.

Comment 3 Romário Rios 2014-03-21 17:22:14 UTC

(In reply to comment #2)
> Please test out beta3 and see if this is still a problem. I'm leaving the
> bug open for now.

I'm not using my laptop right now, so I'm not absolutely sure, but I think the bug was still present after I updated to Beta 3. I will check it later tonight and give you a definitive answer.

Comment 4 André M 2014-03-27 18:57:15 UTC

I'm getting a [maybe] related issue, but I'm unsure it's related with baloo (though I think it is). In htop/top/ps, there's no process consuming a lot of RAM (not even akonadi_baloo_indexer), but my RAM keeps increasing, until consuming almost all my 12G RAM and starting swap flush. I just updated to KDE 4.13beta3, from a up-to-date Arch Linux install, and did a reset of my KDE configs (removed ~/.kde4, ~/.local/share/akonadi). 
I've been asked by polkit to provide authorization for baloo to increase process limit in opened files or something like that, and maybe this issue is related with some sort of "files not being correctly closed by kernel" bug, or something like that. For sure, before updating to KDE 4.13beta from KDE 4.12, I hadn't this kind of issue, and my memory kept well-behaved for long periods of uptime. Do you guys know how to track which process (and confirm if it's related with baloo) keeps eating my RAM and not being shown in ps?

Comment 5 Vishesh Handa 2014-04-07 11:07:08 UTC

definitely fixed with the latest release.