On 8/12/20 2:27 PM, Sergio Belkin wrote:
Hi!
I 've just had a problem using EarlyOOM + ZRAM. I haven't a disk-based
swap partition.
I was using mainly Zoom (desktop app) + Firefox + VirtualBox (Debian
with 4GB of RAM), and EarlyOOM killed Zoom in the middle of a call :(
This is weird---your swap was 100% full, and ram almost full, and yet
killing 4GB VirtualBox didn't seem to free up memory. I suspect some
sort of measurement or reporting error---if these numbers were accurate,
EarlyOOM did have a reason to panic and kill zoom. BTW, zoom taking 721
MiB is crazy.
One possibility that comes to mind is that there's a process not
mentioned in the log (some system process???) that keeps allocating
memory as soon as it is freed by EarlyOOM, so killing the processes does
not result in increasing free memory (the first column).
399 of 15887 MiB ( 2.51%) SIGTERM "Web Content": badness 315, VmRSS 313 MiB
397 of 15887 MiB ( 2.50%) SIGTERM "Web Content": badness 304, VmRSS 80 MiB
379 of 15887 MiB ( 2.39%) SIGTERM "Web Content": badness 303, VmRSS 74 MiB
335 of 15887 MiB ( 2.11%) SIGTERM "Web Content": badness 303, VmRSS 70 MiB
315 of 15887 MiB ( 1.98%) SIGTERM "Web Content": badness 301, VmRSS 27 MiB
288 of 15887 MiB ( 1.81%) SIGTERM "VirtualBoxVM":badness 212, VmRSS 4244 MiB
337 of 15887 MiB ( 2.13%) SIGTERM "zoom": badness 36, VmRSS 721 MiB
Note how the full log helpfully mentions the actual tresholds for
SIGTERM: mem 2.52%, swap 10%, Where does 2.52 come from, pray?
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
