Bug 305352

Summary:	A process called "akonadi_nepomuk_feeder" eats my RAM after startup.
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Ettore Atalan <atalanttore>
Component:	Nepomuk Feeder Agents	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	critical	CC:	adaptee, atalanttore, hpj, me, vkrause
Priority:	NOR
Version:	4.9
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:	4.11
Sentry Crash Report:
Attachments:	/home/***/.config/akonadi/ New crash information added by DrKonqi akonadi_nepomuk_feeder memory usage top screenshot showing akonadi craziness

Description Ettore Atalan 2012-08-17 20:09:09 UTC

I'm using KDE 4.9.0 on Kubuntu 12.04 x64.

There is a big problem since an update last week. A process called "akonadi_nepomuk_feeder" eats my RAM after startup. The process takes around 100 MB per second (!) until it has all of my 4GB RAM and my whole computer freezes. This all happens in barely a minute.


Regards,
Ettore Atalan

Reproducible: Always

Steps to Reproduce:
1. Normal startup
2. Wait until the computer freezes
3. This takes not even a minute.
Actual Results:  
The whole computer freezes.

Expected Results:  
Normal RAM usage and no freezing.

Comment 1 Christophe Marin 2012-08-17 22:27:24 UTC

Please check if https://bugs.kde.org/show_bug.cgi?id=298257 helps

Comment 2 Ettore Atalan 2012-08-18 11:09:33 UTC

Created attachment 73270 [details]
/home/***/.config/akonadi/

Unfortunately, there is no "agent_config_akonadi_mailfilter_agent_changes.dat" on my computer.

Comment 3 Ettore Atalan 2012-08-19 11:31:56 UTC

Created attachment 73290 [details]
New crash information added by DrKonqi

akonadi_maildispatcher_agent (4.9) on KDE Platform 4.9.00 using Qt 4.8.1

- What I was doing when the application crashed:

I was killing akonadi_nepomuk_feeder, because it was eating my whole RAM again after startup.

-- Backtrace (Reduced):
#6  0x00007fd2bece8445 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fd2becebbab in __GI_abort () at abort.c:91
[...]
#9  0x00007fd2c20c1036 in ~QDebug (this=0x7fffb3e4a1f0, __in_chrg=<optimized out>) at /usr/include/qt4/QtCore/qdebug.h:85
#10 Akonadi::AgentBasePrivate::delayedInit (this=0x2623c80) at ../../akonadi/agentbase.cpp:289
#11 0x00007fd2c20c1f3a in Akonadi::AgentBase::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./agentbase.moc:97

Comment 4 Ettore Atalan 2012-08-19 12:16:56 UTC

Created attachment 73293 [details]
akonadi_nepomuk_feeder memory usage

Comment 5 Christophe Marin 2012-08-19 14:55:16 UTC

If it's the nepomuk feeder that starts eating all memory, you have to rename the matching .dat file (ie agent_config_akonadi_nepomuk_feeder_changes.dat)

Comment 6 Ettore Atalan 2012-08-21 10:55:29 UTC

It worked out!

Renaming agent_config_akonadi_nepomuk_feeder_changes.dat in agent_config_akonadi_nepomuk_feeder_changes.dat_old and the problems are gone.

Comment 7 Abel Deuring 2013-01-23 21:54:04 UTC

Created attachment 76672 [details]
top screenshot showing akonadi craziness

sorry to be so blunt, but this bug is really mad.

Attached is a "screenshot" from top when akonadi went crazy on a machine with 32GB memory. I was barely able to start "top"; an attempt to activate another terminal window in order to start emacs and to copy&paste the content of the top window failed with a "human timeout" after a few minutes. So here is a 

I've seen this a few times on different machines since a few years, but I'd though that 32 GB should be plenty, even for akonadi...

Time to kill akonadi & friends on the file system, i.e. to replace them with a link to /bin/false and to run chattr +i on the links.

Comment 8 markuss 2013-02-12 17:37:30 UTC

*** Bug 312813 has been marked as a duplicate of this bug. ***

Comment 9 Vishesh Handa 2013-08-17 11:36:24 UTC

With 4.11 change recording has been disabled so this issue should never occur.