https://bugs.kde.org/show_bug.cgi?id=460460
--- Comment #10 from tagwer...@innerjoin.org ---
(In reply to Adam Fontenot from comment #9)
> I wonder, though, whether the specific issue reported here has been fixed?
> That is, *if* baloo_file has hung on some file, does `balooctl` still hang,
> and / or misreport its status as "idle"? Granted, these hangs should be much
> less common now, but if one does occur, it would be nice to know the
> situation is correctly reported to the user and can be stopped by pausing /
> disabling the indexer from the UI.
There's been this...
https://invent.kde.org/frameworks/baloo/-/merge_requests/174
I'm not sure whether it's talking about exactly your problem but it seems to
catch one of the edge cases.
My experience is that the limit on RAM (and stopping Baloo swapping) is a game
changer... People were focused on CPU use whereas really a lot of the
performance hit was memory related.
--
You are receiving this mail because:
You are watching all bug changes.
