I've been struggling with this bug for nearly a week and only now found this issue. Thanks for fixing it!
For the sake of others finding it, here's the stack trace part of the oom-killer log, which contains some terms I searched for a while ago that aren't mentioned here yet.
I've been struggling with this bug for nearly a week and only now found this issue. Thanks for fixing it!
For the sake of others finding it, here's the stack trace part of the oom-killer log, which contains some terms I searched for a while ago that aren't mentioned here yet.
docker invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=-1000 7c63>] dump_stack+ 0x63/0x90 ad4e>] dump_header+ 0x5a/0x1c5 26c2>] oom_kill_ process+ 0x202/0x3c0 2ae9>] out_of_ memory+ 0x219/0x460 8a5d>] __alloc_ pages_slowpath. constprop. 88+0x8fd/ 0xa70 8e56>] __alloc_ pages_nodemask+ 0x286/0x2a0 8f0b>] alloc_kmem_ pages_node+ 0x4b/0xc0 ea5e>] copy_process+ 0x1be/0x1b70 225c>] ? apparmor_ file_alloc_ security+ 0x5c/0x220 d04a>] ? kmem_cache_ alloc+0x1ca/ 0x1f0 8263>] ? security_ file_alloc+ 0x33/0x50 aeb1>] ? __raw_callee_ save___ pv_queued_ spin_unlock+ 0x11/0x20 05a0>] _do_fork+0x80/0x360 0929>] SyS_clone+0x19/0x20 85f2>] entry_SYSCALL_ 64_fastpath+ 0x16/0x71
docker cpuset=/ mems_allowed=0
CPU: 11 PID: 4472 Comm: docker Tainted: G W 4.4.0-62-generic #83-Ubuntu
Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016
0000000000000286 0000000057f64c94 ffff880dfb5efaf0 ffffffff813f7c63
ffff880dfb5efcc8 ffff880fbfda0000 ffff880dfb5efb60 ffffffff8120ad4e
ffffffff81cd2d7f 0000000000000000 ffffffff81e67760 0000000000000206
Call Trace:
[<ffffffff813f
[<ffffffff8120
[<ffffffff8119
[<ffffffff8119
[<ffffffff8119
[<ffffffff8119
[<ffffffff8119
[<ffffffff8107
[<ffffffff8139
[<ffffffff811e
[<ffffffff8134
[<ffffffff810c
[<ffffffff8108
[<ffffffff8108
[<ffffffff8183