https://bugs.kde.org/show_bug.cgi?id=474346
Branimir Amidzic <m...@ambraspace.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOT A BUG
Status|REPORTED |RESOLVED
--- Comment #2 from Branimir Amidzic <m...@ambraspace.com> ---
(In reply to tagwerk19 from comment #1)
> Two things to check...
>
> Is baloo running with the systemd memory limits? There's been a recent
> change to limit baloo to using 512 MB. You can check with:
> $ systemctl status --user kde-baloo
> and look at "high" value in the "Memory:" line.
>
> This can tip baloo_file and baloo_file_extractor over to using swap. Have a
> look at:
> https://bugs.kde.org/show_bug.cgi?id=470382#c1
>
> It's also possible you are hitting a file that does not want to be indexed.
> Baloo_file_extractor tries to get readable text out of a file and some times
> this just does not work in the time and space available (examples being a
> multi-gigabyte .mbox file or large scientific graphs in a PDF). You would
> need to watch, with "balooctl monitor" what was being indexed.
Thanks! It seems this was false alarm.
I guess that baloo_file_extractor behaves this way only when indexing files.
Now, after it has finished indexing, the swap usage is back to 0%.
Sorry for raising flags...
--
You are receiving this mail because:
You are watching all bug changes.
