Reply to topic

[FIXED] baloo-file using 100% of a CPU core

User avatar sparhawk
Registered Member
Posts
399
Karma
0
OS
I've just upgraded to Kubuntu 14.10 with KDE 4.12.95. For about the last 12 hours, baloo-file has been using up 100% of a CPU core.

Is this just initial indexing? It's been going for a bit longer than I expected.

Thinking that I might speed it up, I attempted to migrate nepomuk data across. However, after running `nepomukbaloomigrator` I was told `Data already migrated. Quitting` (and then it crashed).

Last edited by sparhawk on Mon Apr 07, 2014 12:46 pm, edited 3 times in total.
User avatar bcooksley
Administrator
Posts
19759
Karma
86
OS
Can you use the lsof utility to see if the baloo-file process is still accessing the same file?
If so, it may be hung indexing the same file.

Also, try checking to see if the PID is staying the same, or changing constantly - if it is changing then that is indicative that it is crashing.


KDE Sysadmin
[img]http://forum.kde.org/content/bcooksley_sig.png[/img]
User avatar sparhawk
Registered Member
Posts
399
Karma
0
OS
Hmm… it actually stopped after working hard for 12–24 hours. I killed it a few times when my fan got annoying, so I suspect that the pid was constant..

Thanks anyway for the help.
User avatar sparhawk
Registered Member
Posts
399
Karma
0
OS
Hm… so it's doing it again. I was having a look at system settings, and noticed that my home folder was excluded from "Desktop Search". I enabled it, and baloo_file started using 100% of a core again.

It seems to be the same pid (for the last 20 minutes). There are a few other processes called baloo_file_extractor that are also active.

lsof gives me many files, so I'm not sure what I should be looking at:

Code: Select all
$ lsof|grep baloo_fil | wc -l
1568


However, I saved the lsof output to a file, then compared the output from a few minutes later. Both outputs were identical.

==EDIT==
From /var/log/kern.log:

Code: Select all
Apr  5 14:20:14 sparhawk-XPS-17 kernel: [ 6404.553150] baloo_file_extr[13596]: segfault at 10 ip 00007f06eb0c3e78 sp 00007fff8a55f500 error 4 in libxapian.so.22.6.3[7f06eb083000+1ec000]
Apr  5 14:20:17 sparhawk-XPS-17 kernel: [ 6407.624133] baloo_file_extr[13668]: segfault at 10 ip 00007f704a530e78 sp 00007fffd61b8ad0 error 4 in libxapian.so.22.6.3[7f704a4f0000+1ec000]
Apr  5 14:20:24 sparhawk-XPS-17 kernel: [ 6414.940112] baloo_file_extr[13732]: segfault at 10 ip 00007fc1388f3e78 sp 00007fff639ccd20 error 4 in libxapian.so.22.6.3[7fc1388b3000+1ec000]
Apr  5 14:20:25 sparhawk-XPS-17 kernel: [ 6415.271757] baloo_file_extr[13742]: segfault at 10 ip 00007f87b67c4e78 sp 00007fff4efce610 error 4 in libxapian.so.22.6.3[7f87b6784000+1ec000]
Apr  5 14:25:14 sparhawk-XPS-17 kernel: [ 6705.326377] baloo_file_extr[14139]: segfault at 10 ip 00007f2691484e78 sp 00007fff26d92a20 error 4 in libxapian.so.22.6.3[7f2691444000+1ec000]
Apr  5 14:25:15 sparhawk-XPS-17 kernel: [ 6706.015471] baloo_file_extr[14153]: segfault at 10 ip 00007f9f0ab7ae78 sp 00007fff701e71a0 error 4 in libxapian.so.22.6.3[7f9f0ab3a000+1ec000]
Apr  5 14:25:15 sparhawk-XPS-17 kernel: [ 6706.251464] baloo_file_extr[14172]: segfault at 10 ip 00007f0712dc1e78 sp 00007fff69b37530 error 4 in libxapian.so.22.6.3[7f0712d81000+1ec000]
Apr  5 14:25:15 sparhawk-XPS-17 kernel: [ 6706.474818] baloo_file_extr[14178]: segfault at 10 ip 00007f661651ae78 sp 00007fffffcb4820 error 4 in libxapian.so.22.6.3[7f66164da000+1ec000]
Apr  5 14:25:16 sparhawk-XPS-17 kernel: [ 6706.540793] baloo_file_extr[14179]: segfault at 10 ip 00007fc451962e78 sp 00007fffd909f250 error 4 in libxapian.so.22.6.3[7fc451922000+1ec000]
Apr  5 14:25:16 sparhawk-XPS-17 kernel: [ 6706.585564] baloo_file_extr[14180]: segfault at 10 ip 00007fbc3cd58e78 sp 00007fffa263d9d0 error 4 in libxapian.so.22.6.3[7fbc3cd18000+1ec000]
Apr  5 14:25:16 sparhawk-XPS-17 kernel: [ 6707.127538] baloo_file_extr[14215]: segfault at 10 ip 00007fbc27299e78 sp 00007ffffb327360 error 4 in libxapian.so.22.6.3[7fbc27259000+1ec000]
Apr  5 14:46:01 sparhawk-XPS-17 kernel: [ 7952.652368] baloo_file_extr[16009]: segfault at 10 ip 00007f16289a9e78 sp 00007fff4fb2fd40 error 4 in libxapian.so.22.6.3[7f1628969000+1ec000]
Apr  5 14:46:01 sparhawk-XPS-17 kernel: [ 7952.874949] baloo_file_extr[16015]: segfault at 10 ip 00007f6724329e78 sp 00007fffba0e08b0 error 4 in libxapian.so.22.6.3[7f67242e9000+1ec000]
Apr  5 14:51:01 sparhawk-XPS-17 kernel: [ 8252.912454] baloo_file_extr[16381]: segfault at 10 ip 00007eff696b0e78 sp 00007fffa4814880 error 4 in libxapian.so.22.6.3[7eff69670000+1ec000]
Apr  5 14:51:01 sparhawk-XPS-17 kernel: [ 8253.183379] baloo_file_extr[16401]: segfault at 10 ip 00007fcba29e1e78 sp 00007fff2ff109d0 error 4 in libxapian.so.22.6.3[7fcba29a1000+1ec000]
Apr  5 14:51:01 sparhawk-XPS-17 kernel: [ 8253.584948] baloo_file_extr[16416]: segfault at 10 ip 00007f77e5d42e78 sp 00007fff7eb85000 error 4 in libxapian.so.22.6.3[7f77e5d02000+1ec000]
Apr  5 14:51:02 sparhawk-XPS-17 kernel: [ 8253.832379] baloo_file_extr[16436]: segfault at 10 ip 00007f8d206aae78 sp 00007fff97616790 error 4 in libxapian.so.22.6.3[7f8d2066a000+1ec000]
Apr  5 14:51:02 sparhawk-XPS-17 kernel: [ 8253.876213] baloo_file_extr[16437]: segfault at 10 ip 00007fc4f4fdae78 sp 00007fff11529230 error 4 in libxapian.so.22.6.3[7fc4f4f9a000+1ec000]
Apr  5 14:51:02 sparhawk-XPS-17 kernel: [ 8254.094994] baloo_file_extr[16446]: segfault at 10 ip 00007fcc30520e78 sp 00007fff229e1fa0 error 4 in libxapian.so.22.6.3[7fcc304e0000+1ec000]
Apr  5 14:51:03 sparhawk-XPS-17 kernel: [ 8255.542120] baloo_file_extr[16479]: segfault at 10 ip 00007f532a9e2e78 sp 00007fffec637820 error 4 in libxapian.so.22.6.3[7f532a9a2000+1ec000]
Apr  5 14:51:03 sparhawk-XPS-17 kernel: [ 8255.792164] baloo_file_extr[16484]: segfault at 10 ip 00007f0355339e78 sp 00007fff28e89ca0 error 4 in libxapian.so.22.6.3[7f03552f9000+1ec000]
Apr  5 14:56:01 sparhawk-XPS-17 kernel: [ 8553.742484] baloo_file_extr[16917]: segfault at 10 ip 00007ff2235d0e78 sp 00007fff62960a20 error 4 in libxapian.so.22.6.3[7ff223590000+1ec000]
Apr  5 14:56:01 sparhawk-XPS-17 kernel: [ 8553.961348] baloo_file_extr[16932]: segfault at 10 ip 00007f42d51a2e78 sp 00007fff844772f0 error 4 in libxapian.so.22.6.3[7f42d5162000+1ec000]
Apr  5 14:56:02 sparhawk-XPS-17 kernel: [ 8554.430662] baloo_file_extr[16964]: segfault at 10 ip 00007ff04f2abe78 sp 00007fff825687c0 error 4 in libxapian.so.22.6.3[7ff04f26b000+1ec000]
Apr  5 14:56:02 sparhawk-XPS-17 kernel: [ 8554.483884] baloo_file_extr[16965]: segfault at 10 ip 00007f4699745e78 sp 00007fff6e3bdc60 error 4 in libxapian.so.22.6.3[7f4699705000+1ec000]
Apr  5 14:56:03 sparhawk-XPS-17 kernel: [ 8555.134485] baloo_file_extr[16998]: segfault at 10 ip 00007fa843627e78 sp 00007fff018ade20 error 4 in libxapian.so.22.6.3[7fa8435e7000+1ec000]
Apr  5 14:56:03 sparhawk-XPS-17 kernel: [ 8555.221054] baloo_file_extr[17001]: segfault at 10 ip 00007f14085efe78 sp 00007fff4dbe23f0 error 4 in libxapian.so.22.6.3[7f14085af000+1ec000]
Apr  5 14:56:03 sparhawk-XPS-17 kernel: [ 8555.555538] baloo_file_extr[17024]: segfault at 10 ip 00007feaf7face78 sp 00007fff54b81ff0 error 4 in libxapian.so.22.6.3[7feaf7f6c000+1ec000]


==EDIT2==
Someone else sees it too.
User avatar bcooksley
Administrator
Posts
19759
Karma
86
OS
Can you please check the PID of the baloo_file_extractor processes, as well as the arguments passed to them?
If they are restarting extremely frequently, then this could explain the high CPU usage.

In terms of the crashes, those are in libxapian, are you able to gather a backtrace somehow?
If DrKonqi is not being launched, you may need to enable core files, and generate a backtrace from one of them. This backtrace will allow us to verify that the Xapian libraries are at fault.


KDE Sysadmin
[img]http://forum.kde.org/content/bcooksley_sig.png[/img]
dilfridge
Registered Member
Posts
4
Karma
0
OS
See also https://bugs.kde.org/show_bug.cgi?id=333133
Which exact version of xapian are you using?
User avatar vHanda
KDE Developer
Posts
84
Karma
0
OS
I've fixed the baloo_file at 100% problem, and the relevant code for the xapian crash has been refactored. It should no longer crash.
User avatar sparhawk
Registered Member
Posts
399
Karma
0
OS
vHanda wrote:I've fixed the baloo_file at 100% problem, and the relevant code for the xapian crash has been refactored. It should no longer crash.


Thanks for that. I'd actually dispaired and disabled baloo with "Hidden=True" in baloo_file.desktop, but I'll reenable it when the fix comes through. Cheers.
Nerdfest
Registered Member
Posts
3
Karma
0
What release is the fix going out in?
User avatar einar
Administrator
Posts
3399
Karma
7
OS
4.13 final should have it.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
chrisvdb
Registered Member
Posts
1
Karma
0
I'm running KDE 4.13 on Kubuntu 14.04 and I have baloo using 100% of a cpu core as well. I killed it after 15 min or so.

Chris.
User avatar einar
Administrator
Posts
3399
Karma
7
OS
Is it like the original problem, where the 100% CPU usage is due to segfaults? If not, please open a separate thread about this issue.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
User avatar vHanda
KDE Developer
Posts
84
Karma
0
OS
This is a new issue that has cropped up. It seems we are using newer features of Xapian which are causing the database to get corrupted.

The only way to fix it now is to run -
$ balooctl disable
$ balooctl enable

This will reset the database and restart it.
User avatar sparhawk
Registered Member
Posts
399
Karma
0
OS
vHanda wrote:This is a new issue that has cropped up. It seems we are using newer features of Xapian which are causing the database to get corrupted.

The only way to fix it now is to run -
$ balooctl disable
$ balooctl enable

This will reset the database and restart it.


vHanda, are you replying to chrisvdb (from ten months ago), or to all of us? Are you saying that chrisvdb should reset/restart the database if they are still experiencing 100% CPU usage, or are you saying that all of us should reset/restart it, because of other problems?
cjulio
Registered Member
Posts
1
Karma
0
Hola!

I found the cause, in my case, was causing the use of 100% of a CPU.
Was the ~ / .xsession-errors file which is permanently growing and writing tons of debug information.
I deleted that file and the problem disappeared.

Now all I need to know is why that file is logging so many details of the session. :-\
Apparently it's a problem for baloo when it finds files that are continually updated.


Kubuntu 15.04 fresh install + dist-update

Best regards.

 
Reply to topic

Bookmarks



Who is online

Registered users: alfredod, Baidu [Spider], Bing [Bot], crozbo, dmiroshnichenko, Exabot [Bot], Google [Bot], jackdinn, Majestic-12 [Bot], nazarnirvana, nocin, paviluf, Sogou [Bot], subGlitch, Yahoo [Bot]