This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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

--- Comment #13 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Sumeet Keswani from comment #12)

> "Can you reproduce the issue with more recent glibc versions than what's in
>  Red Hat Enterprise Linux 6?" 
> - yes we are able to reproduce this with glibc-2.12.1-192 which is the most
> recent glibc in RHEL 6.x

That doesn't really answer my question.  I'm interested in the behavior of the
current upstream sources (master branch or any of the recent release branches
would be fine).

If you don't want to work with upstream sources, we should perhaps move the
conversation to the bug in Red Hat Bugzilla because glibc 2.12 is not terribly
relevant to the glibc upstream community at this point (that release happened
more than five years ago).

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]