Bug 278332

Summary: Process Akonadi_Agent_launcher has too many copies in memory
Product: [Frameworks and Libraries] Akonadi Reporter: Igor Strelnikoff <Freiheits>
Component: MigrationAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: amantia, germano.massullo, sonichedgehog_hyperblast00
Priority: NOR    
Version: 4.7   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: 1
2
3
System monitor screenshot

Description Igor Strelnikoff 2011-07-23 13:54:47 UTC
Version:           4.7 (using Devel) 
OS:                Linux

С языка:
русский
 
На:
английский
 
Перевод текстов и веб-страниц
Возможно, вы имели в виду: Процесс Akonadi Agent лаунчер при работе издает в памяти порядка
Разрешить написание латиницей
Введите текст или адрес веб-сайта либо переведите документ.
Отмена
Прослушать
На латинице
Protsess Akonady_Agent_launcher pri rabote sozdaet v pamyati poryadka 30-40 svoih kopiĭ i ya podozrevayu chto ih kolichestvo so vremenem uvelichivaet·sya. Smotri skrinshoty PS Inogda takoe sluchaet·sya i v 4.6.x prichinu ustanovitʹ ya ne mogu 1 Obnovitʹ KDE do versii 4.6.95 2 vklyuchitʹ Akonady i nepomuk
Перевод: русский > английский
Akonady_Agent_launcher process at work is created in memory of the order of 30-40 copies and I suspect that their number increases with time. See screenshots

PS Sometimes it happens in the 4.6.x and the reason I can not install

Reproducible: Always

Steps to Reproduce:
1 Update to version 4.6.95 KDE
2 to include Akonady and Nepomuk


Expected Results:  
I think there should be one process in memory
Comment 1 Igor Strelnikoff 2011-07-23 13:56:25 UTC
Akonady_Agent_launcher process at work is created in memory of the order of
30-40 copies and I suspect that their number increases with time. See
screenshots

PS Sometimes it happens in the 4.6.x and the reason I can not install
Comment 2 Igor Strelnikoff 2011-07-23 13:57:12 UTC
Created attachment 62116 [details]
1
Comment 3 Igor Strelnikoff 2011-07-23 13:58:01 UTC
Created attachment 62117 [details]
2
Comment 4 Igor Strelnikoff 2011-07-23 13:58:45 UTC
Created attachment 62118 [details]
3
Comment 5 Christophe Marin 2011-08-30 16:14:27 UTC
probably means the migration went wrong and you now have duplicate resources. You can clean your configured resources in systemsettings / "Personal Information"
Comment 6 Igor Strelnikoff 2011-09-18 13:01:47 UTC
There is only the item "Default Address Book"
Comment 7 András Manţia 2011-09-22 06:15:46 UTC
Run akonadiconsole and remove the unneeded resources.
Comment 8 Germano Massullo 2011-11-17 09:56:34 UTC
I can confirm that.
I was using Valgrind to debug a C program that I am developing, when it saturated my ram. So I opened system monitor to check processes, and I saw also a lot of akonadi processes.
Here I attatch the screenshot.

Fedora 16 KDE 4.7.3 32bit Kernel 3.1.1-1.fc16.i686
Comment 9 Germano Massullo 2011-11-17 09:58:21 UTC
Created attachment 65778 [details]
System monitor screenshot
Comment 10 Mircea Kitsune 2012-10-03 09:49:13 UTC
Confirmed. openSUSE 12.2 64bit KDE 4.8.5. I have about 40 akonadi_agent_launcher processes too in System Monitor, each taking about 4.000 K of memory. No idea what exactly causes it yet in Akonadi settings.
Comment 11 Mircea Kitsune 2012-10-03 12:31:06 UTC
[SOLVED / WORKAROUND]

I found the cause for this problem (at least what it was for me). Go to the Akonadi Configuration menu and the Akonadi Resource Configuration tab. Each entry in that list will spawn an akonadi_agent_launcher process. In my case I had about 40 which were duplicates, abandoned and / or useless. I deleted them and only kept 5. Now I have only 5 akonadi_agent_launcher processes, and a few others that begin with akonadi.

So if there's a bug, it's why so many orphaned entries are added to that list. But that could have been other applications adding them there or something... no idea.
Comment 12 Denis Kurz 2016-09-24 20:42:29 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 13 Denis Kurz 2017-01-07 22:07:25 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.