https://bugs.kde.org/show_bug.cgi?id=442453

            Bug ID: 442453
           Summary: Significant amount of disk write in short time after
                    deleting many files in monitored folder.
           Product: frameworks-baloo
           Version: 5.85.0
          Platform: Manjaro
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: Baloo File Daemon
          Assignee: baloo-bugs-n...@kde.org
          Reporter: cantf...@gmail.com
  Target Milestone: ---

SUMMARY

I was deleting quite a bit of files from my home folder (not adding anything,
not moving anything - deleting with ctrl+shift+del so not even moving to
recycle bin). 

baloo_file process consumed about 50% of a single core, and wrote 20-100 Mega
Bytes per second for at least several minutes, reaching a size of index of more
than 6GB.

Not sure I can reproduce it again, though.


STEPS TO REPRODUCE
1. delete files from monitored folder, or move files to a different
(unmonitored disk)?

OBSERVED RESULT

baloo_file process wrote a lot of data, and used up a lot of CPU for a while.
Even though balooctl status reported it was idle.

The balooctl status command took about half a minute to print the data, and
balooctl monitor didn't show any activity while running from a different tab
the status command.


EXPECTED RESULT

To not increase the index size while indexed files decrease...


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION


here are the results of 2 subsequent runs of balooctl status:

Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 199,551
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 5.95 GiB


Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 199,109
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 6.42 GiB

Even though, the time between running these two commands was about a minute,
the size of index grew by  about 500MB, while the Total files indexed number
went down...

Here's the output of balooctl monitor:

Press ctrl+c to stop monitoring
File indexer is running
Idle

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to