You are not logged in.

#1 2013-06-08 10:01:50

gondsman
Member
Registered: 2009-07-27
Posts: 84

[KDE] nepomukfileindexer segfault

Hello everyone,
this problem is a bit complicated for me to explain, so bear with me. smile
Since a couple of days I notice nepomukindexer crashing quite often. Basically if I keep file indexing turned on, even after the system is done indexing everything in my home (it shows "indexer is idle"), after an hour or so I notice my system's CPU usage skyrocketing. It's because of systemd-journalctl, which is spamming the log with the message "Process XXXX (nepomukindexer) dumped core." (where XXXX is always changing). If I check with top, there are hundreds of processes called systemd-coredump and they keep getting spawned, forcing me to reboot my system. If I check the journal, I can also read "nepomukindexer[2800]: segfault at 0 ip 00007f3a5dc0c591 sp 00007fffad123b00 error 4 in libc-2.17.so[7f3a5dba2000+1a3000]".
Anyone else is having this issue? Also, how can I check the log of nepomukindexer, to see if there's a particular file that makes it crash? I can't seem to find it anywhere.
Thanks!

Offline

#2 2013-06-13 13:02:43

martinsbb
Member
Registered: 2013-06-13
Posts: 1

Re: [KDE] nepomukfileindexer segfault

Yes, I am having a very similar issue like gondsman's as well.
I am not 100% sure, but it seems that these high CPU usages start after locking and unlocking the computer.

Offline

#3 2013-08-21 08:53:07

johnnik
Member
Registered: 2012-10-31
Posts: 5

Re: [KDE] nepomukfileindexer segfault

I guess I'll have to bring this back up again but I am having the exact same issues.
High CPU usage due to systemd-journald with journal showing segfaults of nepomukindexer such as:

nepomukindexer[13183]: segfault at 560 ip 00007f764b9cf6a6 sp 00007fffe7e8de90 error 4 in libQtGui.so.4.8.5[7f764b5da000+a5e000]
or
systemd-coredump[13187]: Process 13183 (nepomukindexer) dumped core.

Any ideas? Was it solved for the first ones posted?

Thanks

Offline

#4 2013-08-22 07:07:30

quantumphaze
Member
From: Melbourne, Australia
Registered: 2008-11-14
Posts: 169

Re: [KDE] nepomukfileindexer segfault

It's happening to me here too.

nepomukindexer dies and gets respawned. This causes a new process, systemd-coredump (eats 15MB of RAM), to be created. If you wait a while then systemd-journald will process something and the systemd-coredump will terminate, however the new nepomukindexer soon dies. Since nepomukindexer dies and respawns faster than systemd-journald can terminate the systemd-coredumps I end up with heaps of these 15MB processes sitting in the queue, hitting swap.

You can killall systemd-coredump since they are owned by your user once you see it start.

I can also confirm that the indexer only runs when the screen-locker is on


▁▂▃▄▅▆▇█▉▊▋▌▍▎▏▏▎▍▌▋▊▉█▇▆▅▄▃▂▁

Offline

#5 2013-08-23 15:06:12

rogerrabbig
Member
Registered: 2013-07-04
Posts: 1

Re: [KDE] nepomukfileindexer segfault

I have the exact same issue as well. It is very annoying systemd-journald eats about 25% of my CPU.

Offline

#6 2013-09-03 11:30:21

ReedWood
Member
From: Germany
Registered: 2010-07-12
Posts: 21

Re: [KDE] nepomukfileindexer segfault

Same for me. If I untick "Enable Nepomuk File Indexer" my system is back to normal. Hence, the issue is with the file indexer not with the mail indexer.

Offline

#7 2013-09-03 14:34:58

donniezazen
Member
From: Salt Lake City
Registered: 2011-06-24
Posts: 671
Website

Re: [KDE] nepomukfileindexer segfault

Offline

#8 2013-09-09 12:58:24

yoburtu
Member
Registered: 2006-06-07
Posts: 103

Re: [KDE] nepomukfileindexer segfault

Hello,

same for me. How can I reindex all my data?.

Regards.

Offline

#9 2013-09-09 15:10:16

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 1,703

Re: [KDE] nepomukfileindexer segfault

yoburtu wrote:

Hello,

same for me. How can I reindex all my data?.

Regards.

qdbus-qt4 org.kde.nepomuk.services.nepomukfileindexer /nepomukfileindexer org.kde.nepomuk.FileIndexer.indexFolder path-to-folder 1 1

Offline

Board footer

Powered by FluxBB