[Bug libc/20425] unbalanced and poor utilization of memory in glibc arenas may cause memory bloat and subsequent OOM

[sumeet.keswani at hpe dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=20425

--- Comment #15 from Sumeet Keswani <sumeet.keswani at hpe dot com> ---
Created attachment 9446
  --> https://sourceware.org/bugzilla/attachment.cgi?id=9446&action=edit
reproducer done on glibc-2.22

Attached reproducer was done on glibc-2.22
It demonstrates the increase in RSS memory.

There are some output files in the tarball that show a local run using the code
provided on the following machine config


[centos@ip-10-147-171-138 ~]$ uname -a
Linux  3.10.0-327.10.1.el7.x86_64 #1 SMP Tue Feb 16 17:03:50 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux

[centos@ip-10-147-171-138 ~]$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                32
On-line CPU(s) list:   0-31
Thread(s) per core:    2
Core(s) per socket:    8
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 62
Model name:            Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz
Stepping:              4
CPU MHz:               2500.074
BogoMIPS:              5263.77
Hypervisor vendor:     Xen
Virtualization type:   full
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              25600K
NUMA node0 CPU(s):     0-7,16-23
NUMA node1 CPU(s):     8-15,24-31

-- 
You are receiving this mail because:
You are on the CC list for the bug.