https://bugs.kde.org/show_bug.cgi?id=354636
Oded Arbel <o...@geek.co.il> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o...@geek.co.il --- Comment #9 from Oded Arbel <o...@geek.co.il> --- For me baloo has been acting up every now and then, and I'd like to finally get to the bottom of this. The behavior is currently catatonic and after posting this issue I will kill baloo but not change any configuration or data, so the behavior can be reproduced if someone wants to continue research on this issue. 1. baloo_file_extractor takes a lot of CPU and memory. Here's its line in htop: ----8<---- PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 74566 odeda 39 19 257G 10.1G 9006M S 102. 32.2 8h02:42 /usr/bin/baloo_file_extractor ----8<---- (its a 4 core system, CPU usage looks like a single thread that tries to take up an entire CPU but is slowed down a bit by IO on my fast NVME and the "over 100%" is a sampling error on the part of htop) 2. `balooctl monitor` shows almost no activity, and from time to time bursts of a couple dozen entries that look like this: ----8<---- Indexing: /home/odeda/.cache/mozilla/firefox/i1m74zv1.default/cache2/entries/CE2BB927E036CFCEE27E7795DFB198E7C41A14B6: Ok ----8<---- It should not be indexing `~/.cache` as `~/.config/baloofilerc` has this: exclude folders[$e]=$HOME/.cache/,$HOME/mnt/,$HOME/snap/,[and a few other things] The weird excluded folder behavior may has something to do with the fact I have a trailing slash on my $HOME: ----8<---- $ balooctl config show excludeFolders kf.baloo: Folder cache: std::vector("/home/odeda//.cache/": excluded, "/home/odeda//snap/": excluded, "/home/odeda//mnt/": excluded, "/home/odeda/": included) /home/odeda//.cache/ /home/odeda//snap/ /home/odeda//mnt/ ----8<---- 3. The index file is huge - about 19GB, which doesn't make a lot of sense to me. `balooctl indexSize` has this to say: ----8<---- File Size: 18.75 GiB Used: 948.13 MiB PostingDB: 2.93 GiB 316.627 % PositionDB: 85.44 MiB 9.011 % DocTerms: 1.39 GiB 149.920 % DocFilenameTerms: 152.72 MiB 16.107 % DocXattrTerms: 8.39 MiB 0.885 % IdTree: 35.69 MiB 3.764 % IdFileName: 175.18 MiB 18.476 % DocTime: 92.85 MiB 9.793 % DocData: 43.49 MiB 4.587 % ContentIndexingDB: 448.00 KiB 0.046 % FailedIdsDB: 0 B 0.000 % MTimeDB: 26.48 MiB 2.793 % ----8<---- and to that I can only say "wahhh?!?!?" Here's also `balooctl status`: ----8<---- Baloo File Indexer is running Indexer state: Indexing file content Total files indexed: 2,103,903 Files waiting for content indexing: 6,832 Files failed to index: 0 Current size of index is 18.75 GiB ----8<---- -- You are receiving this mail because: You are watching all bug changes.