fjmorazan When you disable FIle searching, the process related to baloo stops searching in background for added/deleted files, so when you re-enable the feature probably baloo will begin to index again until hits with some dir/file unreachable and provoke a sudden CPU spike.
It was exactly what happened.
When I began indexing my Calibre library, which contains more than 5000 e-books, the process has greatly increased.
I deactivated a file search. It's a feature I rarely use.
Thank you so much, I learned a lot!