© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
It seems that systemd-oomd is doing what it is supposed to do -- you're running a memory stress test that is exceeding the memory pressure limits set by systemd-oomd, so it is killing the offending cgroup(s). If you want to run the stress tests in a separate cgroup, try making a script called e.g. `stress.sh`, and execute the script with systemd-run:
$ systemd-run --user ./stress.sh
Further, you can always make changes to Ubuntu's default systemd-oomd configuration[1] if it better suits your stress testing environment.
There are some complaints about the current state of "swap kill" in systemd-oomd, but that has been discussed in [2] and [3].
[1] https:/
[2] https:/
[3] https:/