https://bugs.kde.org/show_bug.cgi?id=475707
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to drizzt321 from comment #0)
> ... I notice `baloo_file` process is taking up a relatively large amount of
> memory...
See if you are having problems with changing minor device numbers - possible if
you are running BTRFS. In that case, Baloo can see files "reappear" after a
reboot with a different ID and reindex them.
You can check with "baloosearch -i one-of-your-files" and see if you get
multiple results. The "-i" shows the internal DocID that baloo uses. If you get
multiple results, then that might explain the larger index...
In general baloo pulls pages form its index into memory "as needed" and "for
reading", when indexing a new file the changes to the index are bundled into a
transaction and the database pages marked "dirty" ready to be written when the
transaction is committed. If you are not writing, the pages can be dropped when
anything else wants the memory.
There's been a relatively change to the memory limits (as set in the systemd
unit file for kde-baloo) to cap the memory usage to 512M:
https://invent.kde.org/frameworks/baloo/-/merge_requests/124
maybe this is hasn't reached Debian
--
You are receiving this mail because:
You are watching all bug changes.
