https://bugs.kde.org/show_bug.cgi?id=375131
kafei <matthewisrip...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matthewisrip...@gmail.com
--- Comment #1 from kafei <matthewisrip...@gmail.com> ---
I believe I have also been hit by this bug. Today baloo_file_extractor suddenly
started using 100% CPU and didn't stop.
Running `balooctl status` gave the following output:
Baloo File Indexer is running
Indexer state: Idle
Indexed 11547 / 11548 files
Current size of index is 947.69 MiB
Which looks to me like it's hung on a particular file, but I'm not sure how to
figure out which file that is. The contents of
/proc/baloo_file_extractor_pid/fd gave the following, which didn't seem to
indicate the offending file:
0 -> pipe:[17073]
1 -> pipe:[17074]
10 -> anon_inode:inotify
11 -> /home/matt/.local/share/baloo/index
12 -> /home/matt/.local/share/baloo/index
13 -> /proc/1053/mounts
14 -> socket:[17086]
15 -> socket:[18879]
16 -> /home/matt/.local/share/baloo/index-lock
17 -> /home/matt/.local/share/baloo/index
18 -> /home/matt/.local/share/baloo/index
2 -> pipe:[17075]
3 -> socket:[17080]
4 -> anon_inode:[eventfd]
5 -> anon_inode:[eventfd]
6 -> socket:[17082]
7 -> socket:[17894]
8 -> anon_inode:[eventfd]
9 -> socket:[18877]
Even after restarting, baloo_file_extractor immediately starts and hangs in the
same way. The only way to stop it is to kill the process.
--
You are receiving this mail because:
You are watching all bug changes.
