https://bugs.kde.org/show_bug.cgi?id=380456
Johannes Tiemer <jtie...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|5.34.0 |5.52.0
Platform|Neon Packages |Archlinux Packages
--- Comment #12 from Johannes Tiemer <jtie...@gmail.com> ---
Hey everybody,
since installing the update to version 5.52 on my computer (Arch current), the
baloo file indexer began showing unwanted behaviour again. All directories with
large text files were blacklisted beforehand.
The behaviour found is as before: RAM usage explodes within roughly minute to
fill all of 16GB, since I have no swap, it then freezes my machine by clogging
the RAM … playing "nice" with RAM may be a thing too.
What I found with "balooctl monitor"
- it seemed to plainly ignore that it should _not_ index the windows partition
that I have mounted into my home for convenience
- it seems to begin expand in RAM while reporting that it is checking for
"checking for obsolete index entries"
I let baloo completely recreate its index over a few days when I realised it is
misbehaving again. See my above comment for earlier indexSize:
---
$ balooctl indexSize
Actual Size: 32,88 GiB
Expected Size: 22,85 GiB
PostingDB: 2,31 GiB 81.336 %
PositionDB: 1,48 GiB 51.905 %
DocTerms: 3,71 GiB 130.294 %
DocFilenameTerms: 57,95 MiB 1.989 %
DocXattrTerms: 0 B 0.000 %
IdTree: 7,63 MiB 0.262 %
IdFileName: 40,62 MiB 1.394 %
DocTime: 18,80 MiB 0.645 %
DocData: 53,23 MiB 1.827 %
ContentIndexingDB: 0 B 0.000 %
FailedIdsDB: 0 B 0.000 %
MTimeDB: 10,35 MiB 0.355 %
---
--
You are receiving this mail because:
You are watching all bug changes.
