From owner-freebsd-hackers Fri May 21 12:23:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles521.castles.com [208.214.165.85]) by hub.freebsd.org (Postfix) with ESMTP id 6988B1502C for ; Fri, 21 May 1999 12:23:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA01846; Fri, 21 May 1999 12:21:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905211921.MAA01846@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: amobbs@allstor-sw.co.uk Cc: freebsd-hackers@freebsd.org Subject: Re: Wired memory "leaking" In-reply-to: Your message of "Fri, 21 May 1999 19:34:10 BST." <80256778.006601D6.00@mail.plasmon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 May 1999 12:21:51 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >I've got a problem that my KLD is "leaking" wired memory. > > > >It's not actually growing in size, vmstat -m shows a fairly constant > allocation, >and certainly "high" isn't increasing. It's just that as I use it > more, and more >memory gets wired down, and the system becomes unusable. > [blah] > > Just for the archives, it was, predictably, a memory leak after all. My _vnops.c > wasn't freeing the cn_pnbuf. > > Why Oh Why(tm) is everything else freed for you, but the path buffer is left to > the poor, confused, FS to free? Because you may have reallocated it yourself (eg. following a symbolic link type object). At least, that's the only justification I've come up with. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message