https://bugs.kde.org/show_bug.cgi?id=443693
Adam Fontenot <adam.m.fontenot+...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
--- Comment #3 from Adam Fontenot <adam.m.fontenot+...@gmail.com> ---
This isn't fixed for me. Perhaps it's fixed in some situations but not others?
Let me know if you want me to open a new bug.
Specific situation in which I saw this bug: I was compiling some software. All
eight (virtual) cores on my system were in use. I had htop open and noticed
that despite all cores being at 100%, baloo_file was using about 60% CPU (of
one core) consistently, and more than 10% of my RAM. This despite being nice
19! (Perhaps something wrong with the scheduler, but I haven't looked into it
further.)
I opened the system settings, and Baloo's status said "Idle, 100% complete".
Clicking "Pause Indexer" did nothing. baloo_file continued to run with a pretty
aggressive amount of CPU use given that I was trying to compile some software.
Speculation:
* Baloo can be wrong about whether its indexer is running or not
* When Baloo thinks its indexer is not running, and it is, clicking "Pause
Indexer" will fail to stop the indexer.
SIGTERM sent to baloo_file stopped it successfully.
SOFTWARE/OS VERSIONS (updated)
Linux: Arch Linux x86_64 (kernel 5.18.5)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
--
You are receiving this mail because:
You are watching all bug changes.
