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

Michael <k...@callthecomputerdoctor.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|RESOLVED                    |REOPENED
                 CC|                            |kde@callthecomputerdoctor.c
                   |                            |om
         Resolution|WAITINGFORINFO              |---

--- Comment #5 from Michael <k...@callthecomputerdoctor.com> ---
This is an old bug, but after the recent upgrade to Frameworks 5.80.0, Baloo
gobbles up a tremendous amount of memory as it re-indexes all files in $HOME
folder. It doesn't appear to free memory as it indexes. My system becomes laggy
and unresponsive. 


STEPS TO REPRODUCE

1. You may need a $HOME directory with a lot of files. My personal case is
318GB of data, ~1M files, ~76K subdirectories, of all types of documents,
audio, video.
2. Upgrade to Frameworks 5.80.0, reboot. 
3. Upon logging in, Baloo will want to re-index all files. Use "System Monitor"
to observe baloo_file_extractor and baloo_file. 


OBSERVED RESULT

Notice that the "Shared Memory" attribute of baloo_file_extractor continuously
rises, not staying steady or falling. The "Memory" attribute is similary high
at 1G. In my case Shared Memory gets easily gets to 3.4G and my swap file
becomes 5.4G, with no other apps running.


EXPECTED RESULT

Memory usage of Baloo should not keep rising and affecting the swap file.
Memory usage should be constant.


SOFTWARE/OS VERSIONS

Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-67-generic
OS Type: 64-bit
Graphics Platform: X11
Memory: 7.7 GiB of RAM



ADDITIONAL INFORMATION

I'm attaching some screenshots of System Monitor and htop. Notice the memory,
CPU and swap usage. They all are very high and as a side-effect, my laptop is
not responsive. I had to let it run overnight to finish indexing, but even
then, when I rebooted, it wanted to re-index everything again(!).

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

Reply via email to