From owner-freebsd-questions Thu Jan 2 13:42:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA05496 for questions-outgoing; Thu, 2 Jan 1997 13:42:34 -0800 (PST) Received: from gdi.uoregon.edu (cisco-ts7-line4.uoregon.edu [128.223.150.51]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA05480 for ; Thu, 2 Jan 1997 13:42:30 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.2/8.6.12) with SMTP id NAA00493; Thu, 2 Jan 1997 13:42:16 -0800 (PST) Date: Thu, 2 Jan 1997 13:42:16 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Mark Cheeseman cc: freebsd-questions@freebsd.org Subject: Re: What's eating my memory In-Reply-To: <199701012120.VAA03847@bbq.websource.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 31 Dec 1996, Mark Cheeseman wrote: > What's the best way to diagnose a system (2.1.6.1-R) that is running > out of virtual memory? > > I have a system here that has suddenly taken it upon itself to eat up > all available memory and then (not surprisingly) refuses to do > anything else. I don't recall doing anything much to it recently, so > I'm at a loss to figure out what is doing the dastardly deed. use top (installable as a package or port) and keep an eye on the memory values. Target any apps with an inordinately large value. Netscape, the mbone tools and Xwindows are good memory eaters. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major