https://bugs.kde.org/show_bug.cgi?id=470665
--- Comment #9 from tagwer...@innerjoin.org ---
(In reply to Maximilian Böhm from comment #8)
> ... MemoryHigh=50% has worked somewhat: Now, balooctl monitor shows me a list
> of
> the files it is indexing ...
That's good. One step along the way...
> ... But it does seem to index the full partitions
> again and again. Looks like I am affected from both problems, the memory
> limit and the btrfs issue ...
There is a draft Merge Request here:
https://invent.kde.org/frameworks/baloo/-/merge_requests/131
That proposes a "lightweight" fix, it's nice in that it would not force a purge
and reindex (the internal ID's that baloo uses are still 32 bit) but it isn't a
comprehensive solution.
> ... Don’t KDE devs use modern file systems? ...
I'm not sure I'm the right person to answer that one :-) I imagine though, if
you are developing, you want a completely stable, reliable base system. No
extra unknowns. You would then test in different environments.
What interesting is that earlier the BTRFS issue initially caught mostly
OpenSUSE users, that system set up a lot of subvolumes and ran into trouble.
Fedora, also with BTRFS, only rarely showed problems historically but that's
changed with recent releases.
--
You are receiving this mail because:
You are watching all bug changes.
