From owner-freebsd-hackers Fri Sep 12 13:10:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04816 for hackers-outgoing; Fri, 12 Sep 1997 13:10:53 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04811 for ; Fri, 12 Sep 1997 13:10:50 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA07123; Fri, 12 Sep 1997 13:07:25 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd007120; Fri Sep 12 20:07:22 1997 Message-ID: <3419A0D8.7DE14518@whistle.com> Date: Fri, 12 Sep 1997 13:06:48 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Mike Smith CC: Graham Wheeler , hackers@FreeBSD.ORG Subject: Re: Memory leak in getservbyXXX? References: <199709121226.WAA02951@word.smith.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Smith wrote: > > > > If it's a memory leak then it sounds like it's inside the stdio > > > library, possibly in fopen()/fclose(). Without more data it's going to > > > be hard to track this one. > > > > Tell me about it 8-( > > > > It does seem like a memory leak, as the memory use reported by top grows > > over time. I have memory allocation debugging code which confirms that > > I have no leaks in my code (at least of C++ objects), and the fact that > > older sites have been running for months seems to confirm this. > > OK. More to the point then it sounds like it's a memory leak due to > some change in stdio. That's getting slightly easier to chase I they aren't using the threaded libc are they?