https://bugs.kde.org/show_bug.cgi?id=487145
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to niklas312 from comment #0)
> Sometimes, when I compile my program with MAKE, Baloo crashes. I think it
> might get out of RAM? It doesn't always happen when I compile something, but
> with a big project, it happens very regularly.
If you watch with
balooctl monitor
do you see Baloo starting to index something? In the middle of a "make" there
might be many files touched and waiting to be reindexed.
> #13 0x0000772a828c2ac2 in qt_assert
> (assertion=assertion@entry=0x772a82c41201 "id > 0",
> file=file@entry=0x772a82c41193 "./src/engine/transaction.cpp",
> line=line@entry=83) at ./src/corelib/global/qassert.cpp:68
An Assert but I'm not sure what it means 8-)
Possibly that the file has been flagged for indexing but has been deleted
before the indexing is done. If you were on Neon Testing, an assert should
crash you. On Neon User, I'm not so sure...
There's a faint chance that you are hitting the (relatively recent) limit on
the amount of RAM Baloo can use. This is now set in the kde-baloo unit file to
512 MB. You could try giving it more space (this might speed up Baloo)
systemctl --user edit kde-baloo
and changing the
MemoryHigh=512MB
to a percentage depending on how much RAM you've got, 25% would allow Baloo
more room but not steal too much from the rest of the system. Baloo only really
depends on "a lot" of RAM when it is indexing, it can happily use RAM to cache
its database in normal use but will release it when needed.
--
You are receiving this mail because:
You are watching all bug changes.
