Baloo file indexer runs at 100% CPU

[JonathanReeve]

Describe the bug

The Baloo file indexer in KDE is using all my system resources. My CPU runs at 100%, and my fan is running at top speed. My laptop is never like this, unless it's compiling something. This doesn't seem like ordinary behavior, and it's been going on for quite some time.

To Reproduce Steps to reproduce the behavior:

1. Have lots of files
2. Run KDE
3. Notice that your computer is about to die from overheating, since it's been running at 100% CPU for hours.

Expected behavior A clear and concise description of what you expected to happen.

A file indexer wouldn't run this hot.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

Metadata Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

• system: "x86_64-linux"
• host os: Linux 5.4.21, NixOS, 20.09pre214537.39892985b00 (Nightingale)
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.3.3
• channels(jon): "home-manager, home-manager-sway, nixpkgs-20.09pre214168.686274ea62c"
• channels(root): "nixos-20.09pre214537.39892985b00"
• nixpkgs: /home/jon/.nix-defexpr/channels/nixpkgs

Maintainer information:

# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

[matthewbauer]

It's possible it's trying to index the /nix or /tmp directories. I thought that was turned off by defadult though.

[vikanezrimaya]

It's possible it's trying to index the /nix or /tmp directories.

Or maybe your /home is that big :3 Baloo's also a huge memory hog, I usually disable it right away...

[stale[bot]]

I marked this as stale due to inactivity. → More info

[wolfsprite]

Seems to still be an issue, at least in my case where I enabled syncthing to sync with someone that has lots of files. Took a while to figure out what was locking up my system since my system kept locking up. :(

(to confirm, baloo was at the top of htop using significant amount of CPU with multiple processes, even after I had ended the syncthing process)