This is not a bug. It turns out the behaviour I was seeing was due to the fact that swap accounting is disabled by default and so the perl process was swapping rather than being killed when its RAM limit was reached.
If I turn swap off (swapoff -a), the process is killed correctly. Similarly, if I inhibit swapping by setting memory.swappiness to 0 in the "example" cgroup, the process is killed correctly. Alternatively, if I turn swap accounting on (by setting `GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"` in /etc/default/grub, running update-grub, and rebooting), then memory.memsw.* files appear in the "example" cgroup. If I set memory.limit_in_bytes and memory.memsw.limit_in_bytes both to 3000000, then the perl process is killed correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303683 Title: Memory resource controller oom killing not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303683/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
