On zondag 10 december 2017 10:19:24 CET Philipp Huebner wrote: > Looking at syslog after the reboot, I see that oom killer was triggered > several times, as there was no free RAM and no free SWAP left any more. > It also shows that libkscreenlocker5 is using by far the most memory, > and every time oom killer is invoked, libkscreenlocker5 is using even > more memory than before, e.g. total_vm 7549136 -> 7589587. > > For reference: this box has 16 GB of memory + 16 GB of swap and only > runs standard office applications. Sounds like Bug #874581
Attachment:
signature.asc
Description: This is a digitally signed message part.