From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26442 invoked by alias); 13 Oct 2014 03:12:04 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 26392 invoked by uid 48); 13 Oct 2014 03:11:59 -0000 From: "dbavatar at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug network/16001] calls to getaddrinfo() leak memory. Date: Mon, 13 Oct 2014 03:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: network X-Bugzilla-Version: 2.18 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dbavatar at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-10/txt/msg00048.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=16001 --- Comment #4 from Debabrata Banerjee --- (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.