https://bugs.kde.org/show_bug.cgi?id=461256
--- Comment #16 from tagwer...@innerjoin.org ---
(In reply to Alberto Salvia Novella from comment #15)
> Thanks for the help. Let me know if you need more testing.
There was a patch here:
https://invent.kde.org/frameworks/baloo/-/merge_requests/148
that fixes the problem of Baloo "running out" of memory when it starts up (or
maybe after a "balooctl check"); when it is collecting information about all
new/changed files anyway. Previously this info was collected and written to the
index in one transaction, now it is split into multiple small transactions.
It does not directly match your situation, but maybe it has an impact.
--
You are receiving this mail because:
You are watching all bug changes.
