https://bugs.kde.org/show_bug.cgi?id=364858
Bug ID: 364858
Summary: Regression: Re-add a decent way of displaying what
files baloo is indexing / extracting
Product: Baloo
Version: 5.9.90
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: grave
Priority: NOR
Component: General
Assignee: m...@vhanda.in
Reporter: deve...@fuchsnet.ch
CC: pinak.ah...@gmail.com
These days I, again, had an issue with baloo_file_extractor eating all of my
CPU and a lot of my RAM.
It is, at least as far as I was able to tell, completely impossible to debug
that, as baloo no longer prints out what file it is currently indexing /
extracting, and lsof and the likes also don't help.
Please re-add a way to display this, whether it being the inode numbers being
displayed in ps as it used to be or via balooctl or whatever else.
For now the only solution was to, again, completely disable baloo file
indexing.
Reproducible: Always
Steps to Reproduce:
1. Have baloo eat your CPU
2. Try to find out why
Actual Results:
You can't
Expected Results:
You can
--
You are receiving this mail because:
You are watching all bug changes.
