public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dbavatar at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/16001] calls to getaddrinfo() leak memory.
Date: Mon, 13 Oct 2014 03:12:00 -0000 [thread overview]
Message-ID: <bug-16001-131-rBMYg9CcKQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16001-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16001
--- Comment #4 from Debabrata Banerjee <dbavatar at gmail dot com> ---
(In reply to Alexandre Oliva from comment #3)
> I see the testcase duplicates freeaddrinfo behavior, but I don't see how it
> shows there is (or was) any memory leak. I couldn't locate the patch
> submission nor the better ideas about how to fix it to tell whether this
> should be reopened or left closed. Pointers anyone?
Hi, If you create a large number of local interfaces, then you should be able
to reproduce it with the test case attached. i.e. Create 16,000 eth0:xxxxx
aliases and assign a new IPv4 address to each one.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-10-13 3:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 20:14 [Bug network/16001] New: " dbavatar at gmail dot com
2014-06-05 14:24 ` [Bug network/16001] " schwab@linux-m68k.org
2014-06-05 16:04 ` dbavatar at gmail dot com
2014-06-13 12:43 ` fweimer at redhat dot com
2014-09-29 8:17 ` aoliva at sourceware dot org
2014-10-13 3:12 ` dbavatar at gmail dot com [this message]
2014-10-31 7:27 ` aoliva at sourceware dot org
2014-10-31 8:12 ` aoliva at sourceware dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-16001-131-rBMYg9CcKQ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).