SUMMARY I am indexing 100 of Thousands of files with baloo build index. Onces started it consumes quite all CPU Power as well the RAM ressources including swap. With indexing working it is impossible to have any other application working or using in parallel. It thwards performance of any other application quite to zero. Even sometimes the computer appears to be "frozen" because mouse movements are temporarily not possible anymore. But surely it isn't frozen. But not being able to use the computer I have to make a "cold restart" of the computer what is not very good at all. For regular PC work I have to reboot the PC and stopping indexing directly after restart. Indexing I only can do in the night time or any other time not needing the computer. This is very bad!!! It appears having always a "crash" when using KDE baloo indexing Baloo indexing should never consume all capacities of the PC and intelligently adjust its performance /ressources need depending on the need of the other applications. It should work rather in the background. Operating System: Manjaro Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.7.12-1-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 23.4 GiB of RAM + 50 GiB of SWAP Graphics Processor: Mesa Intel® UHD Graphics 620 STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
*** This bug has been marked as a duplicate of bug 418323 ***