Hmm, isn't the "OOM killer enabled" just a notification that OOM killer is working (not taking action)?
I'm running htop now. It seems that baloo really takes too much RAM and CPU, but nothing fatal, plenty of free physical RAM and swap. Anyway, thanks for the tip about baloo, but I think that it'll solve a small part of the problem. On Wed, Jun 24, 2020, 21:03 Michael <confabul...@kintzios.com> wrote: > On Wednesday, 24 June 2020 16:30:25 BST Серега Филатов wrote: > You have OOM messages there. It seems your baloo process eats up all your > RAM > and when the time comes to put the OS to sleep, there is not enough RAM to > do > so. I don't know if using a swap file or swap partition would help, but > controlling how much baloo is indexing will help both in terms of load on > the > CPU as well as in terms of RAM when awake and RAM when you suspend it.
