https://bugs.kde.org/show_bug.cgi?id=498363
--- Comment #4 from Pyx <k...@notpyx.me> --- (In reply to tagwerk19 from comment #2) > (In reply to tagwerk19 from comment #1) > > ... Three possibilities here ... > Did any of the three fit with your situation? > > It would be interesting to know if you purged and restarted the indexing you > got any further. Following on from the second possibility (that Baloo is too > strictly limited by the systemd Ram limits in the unit file), you can quite > safely increase this, have a look at: > https://bugs.kde.org/show_bug.cgi?id=470382#c2 > You can try 25% first (rather than 512M) and see if it makes a difference. Sorry, lost the email to this for a bit. I haven't seen it happen for a bit so I'm assuming it was a weird bug which got fixed by now. -- You are receiving this mail because: You are watching all bug changes.
