https://bugs.kde.org/show_bug.cgi?id=460460
--- Comment #9 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- (In reply to tagwerk19 from comment #8) > (In reply to tagwerk19 from comment #7) > > Slow jobs, shifting sands but maybe quieter waters... > I think a lot of dust has been kicked up and settled again in the last year > with: > https://invent.kde.org/frameworks/baloo/-/merge_requests/131 > for KF6 and cherrypicked for KF5 > https://invent.kde.org/frameworks/baloo/-/merge_requests/169 > > Together with: > https://invent.kde.org/frameworks/baloo/-/merge_requests/121 > and > https://invent.kde.org/frameworks/baloo/-/merge_requests/148 > > I'll leave this open for now, but will set a "WaitingForInfo" at some point. > No rush... I'm inclined to agree that the resource constraining fixes along with my fix https://invent.kde.org/frameworks/baloo/-/merge_requests/96 should have a great impact on Baloo's performance. I'm reenabling content indexing and will submit any issues I encounter. 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 also the related bug 437754 where the act of checking on Baloo's status *causes* high memory use and database bloating. If the UI issues discussed here are mostly downstream of the performance problem, this issue could be closed as a duplicate of that one. -- You are receiving this mail because: You are watching all bug changes.
