https://bugs.kde.org/show_bug.cgi?id=380456
Adam Fontenot <adam.m.fontenot+...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
Ever confirmed|1 |0
--- Comment #24 from Adam Fontenot <adam.m.fontenot+...@gmail.com> ---
With Baloo 6.3.0, I see the following issues, some of which are related to
memory use. As I mentioned over on bug 460460, I just re-enabled Baloo to see
if the issues I previously experienced with it were fixed.
1. After re-enabling Baloo from the System Settings UI, the UI does update to
show the indexer running. Eventually I checked back and indexing appeared to be
hung in a partially complete state, but baloo_file was not running.
2. I cleared the index (balooctl purge), and reenabled the indexer (balooctl
enable).
3. After doing this, Baloo doesn't seem to hang, but bloats memory excessively
(I'm currently seeing over 9 GB used by baloo_file_extractor). The limit set on
the kde-baloo service is unmodified from the default (512 MB), so presumably
enabling Baloo from the terminal has somehow bypassed the systemd service that
is supposed to control it. That seems like a bug that should probably be fixed
(but the memory leak is an issue regardless).
4. The index is once again pretty large, over 8 GB and I'm only about halfway
done with content indexing. If there is a way to debug the index and see which
files are using the most space I would love to provide more details, and this
would allow me to selectively exclude certain directories as well.
I'm returning this issue to "reported" because of the memory problem in (3). I
can tell from strace that baloo_file_extractor is actively scanning files, so
this is *not* an issue where it's gotten hung on one problematic file, and
probably indicates memory that has been leaked.
--
You are receiving this mail because:
You are watching all bug changes.
