KDE 4.12.90, openSuse Today I have baloo_file_extractor more or less always at 100%CPU. Checking why it does that, I found out that I have konversation (chat IRC client) running, which can not connect to the freenode server due to company firewall - which means konversation writes a lot of error log messages into ~/logs/freenode.log - continuously. This obviously leads to the problem that baloo again and again tries to index this logfile. Reproducible: Always Expected Results: The baloo_file_indexer shall be improved to avoid such situation, e.g.: keep an internal list of files which have been reindexed already two times in the last 5 minutes or so (two times to avoid to have ALL files in this list). When a file change is detected for a file in this list, do not immediately reindex the file but wait for another 5 minutes. Timeout should be a sane default, probably let it be configurable in a config file
*** Bug 333954 has been marked as a duplicate of this bug. ***
So, why do you think this is a problem?
I consider using 100% CPU continuously as a problem.
I have a dozen IRC channels open in konversation which are reindexed all the time, but I see no significant CPU load, so your problem is definitely something different.
1) You are testing with KDE 4.12.90, which was the version I originally reported the bug with ? 2) You are also testing in a network which does not reach your IRC servers, as described in my report ? If 2 but not 1, maybe the bug has been already solved.
I hope you're not still using KDE4. That's deprecated and not receiving any bug fixing activity. Are you able to test with a recent version of KDE Frameworks, or build Baloo from source? A lot has happened in five years. :)
I did not say I'm still using that old KDE4 version (actually baloo5-file-5.45.0, openSuse Leap 15.0). I just mentioned that a test with a version different to the reported one might not show the problem anymore. I tried now to simulate the situation by adding data to a text file which I want to index, and so far I see no problem. Let's close this report