Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[KDE] baloo_file_extractor constantly uses > 90% of CPU #2677

Open
softlemonade opened this issue Aug 11, 2024 · 4 comments
Open

[KDE] baloo_file_extractor constantly uses > 90% of CPU #2677

softlemonade opened this issue Aug 11, 2024 · 4 comments

Comments

@softlemonade
Copy link

softlemonade commented Aug 11, 2024

Data for CPU usage:

user@chimerachimera:~ (dotfiles>)$ ps aux  | grep baloo
user      1659  0.3  0.4 268661172 38088 tty7  SNl+ 10:49   0:05 /usr/libexec/kf6/baloo_file

user      2393 89.2 17.7 269079056 1427888 tty7 RNl+ 10:49  24:09 /usr/libexec/kf6/baloo_file_extractor

user      2484  0.0  1.6 268917476 135244 ?    Sl   10:51   0:00 /usr/libexec/baloorunner
user      5111  0.0  0.0 149856   656 pts/0    S+   11:16   0:00 grep baloo

Invocation context. Seems to be unrelated to baloorunner / different execution path.

     |-gdm-+-gdm-session-wor-+-gdm-wayland-ses-+-startplasma-way-+-plasma_session-+-DiscoverNotifie---9*[{DiscoverNotifie}]
     |     |                 |                 |                 |                |-baloo_file-+-baloo_file_extr---5*[{baloo_file_e+
     |     |                 |                 |                 |                |            `-2*[{baloo_file}]
     |     |                 |                 |                 |                |-evolution-alarm---7*[{evolution-alarm}]
--
     |                                 |-at-spi2-registr---3*[{at-spi2-registr}]
     |                                 |-baloorunner---5*[{baloorunner}]
     |                                 |-dbus-daemon

@q66
Copy link
Member

q66 commented Aug 11, 2024

is it actually stuck, or is it just doing stuff? if it's actually stuck, you should attach into it from a debugger

@nekopsykose
Copy link
Member

it's actually stuck and super easy to reproduce (p much just start it or launch kde that starts it, then within 20 minutes it will just be looping on nothing)

the reason it's stuck is different every time, last one i remember is 'some tempfile written by my $EDITOR got written to then renamed into the original file in a microsecond, and baloo saw the tempfile be made and then it got deleted right before being indexed so it got stuck', which is a very funny failure case

@nekopsykose
Copy link
Member

(it also doesn't seem musl related or something, you could disable baloo entirely with balooctl6 disable)

@softlemonade
Copy link
Author

Thanks for the responses, i disabled it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants