Bug 427914 - Kinfo File Indexer Monitor takes lot of CPU when indexing is disabled
Summary: Kinfo File Indexer Monitor takes lot of CPU when indexing is disabled
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kinfocenter
Classification: Applications
Component: File Indexer Monitor (other bugs)
Version First Reported In: 5.20.0
Platform: Neon Linux
: NOR minor
Target Milestone: ---
Assignee: Stefan Brüns
URL:
Keywords: efficiency-and-performance
Depends on:
Blocks:
 
Reported: 2020-10-18 10:36 UTC by Peter Ped Helcmanovsky
Modified: 2022-09-27 20:48 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
system load when viewing the file indexer tab (132.02 KB, image/png)
2020-10-18 10:36 UTC, Peter Ped Helcmanovsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Ped Helcmanovsky 2020-10-18 10:36:13 UTC
Created attachment 132521 [details]
system load when viewing the file indexer tab

SUMMARY
The tab in Kinfo showing status of File Indexer takes 50%+ CPU load even when showing just "File Indexer is not running" with button "Start File Indexer".
(that is 50%+ on *all* 16 cores of AMD Ryzen 7)


STEPS TO REPRODUCE
1. disable file indexing service
2. launch kinfo - normal ~0% CPU usage, showing version of KDE
3. switch to File Indexer Monitor = half the CPU used for "nothing"

OBSERVED RESULT
~35% CPU is used by process kinfocenter

EXPECTED RESULT
~0-1% CPU usage would be expected, when it just reports that the file indexing is not running

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.20
(available in About System)
KDE Plasma Version: 5.20.0
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
kernel: 5.9.1-050901-generic

CPU: 16x AMD Ryzen 7 4800H
Comment 1 Peter Ped Helcmanovsky 2020-10-18 11:31:47 UTC
Hm, seems to be gone after going down to kernel 5.8.0-23 (after noticing some other strange things, like `dmesg` not working, reporting something about denied access).

And also meanwhile I removed the "nomodeset" from grub config (leftover from booting the live image), which seems to help to init the GPU driver correctly during the boot sequence, which may be another change to original report.

So I **guess** that kinfocenter tab may be sensitive either to being denied some system file (like dmesg), or to the SW mode of gfx. (or maybe it's something completely different, as it usually goes with programming and bug reports)
Comment 2 Nate Graham 2020-10-21 03:57:27 UTC
Can confirm. The CPU spike is not as dramatic on my machine, but it is still noticeable. How odd.
Comment 3 Stefan Brüns 2020-10-21 14:00:47 UTC
Seems to be a Neon specific problem, can´t reproduce with Tumbleweed, almost same package versions (Qt is 5.15.1).
Comment 4 Nate Graham 2020-10-21 14:29:02 UTC
I can reproduce on Tumbleweed (with all KDE stuff compiled from source).
Comment 5 Patrick Silva 2021-06-05 15:03:33 UTC
File Indexer Monitor module was removed from Plasma 5.22 beta.
Comment 6 Nate Graham 2022-09-27 20:48:38 UTC
Yep, this page is long dead, its UI having been moved to the relevant page in System Settings. And I can't reproduce the issue there.