Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!newsflash.concordia.ca!sifon!homer.cs.mcgill.ca!storm From: storm@cs.mcgill.ca (Marc WANDSCHNEIDER) Newsgroups: comp.os.386bsd.apps Subject: Re: Top - what is it and do I need it? Date: 10 Jan 1994 21:28:40 GMT Organization: SOCS, McGill University, Montreal, Canada Lines: 35 Message-ID: <2gsha9$1ri@homer.cs.mcgill.ca> References: <CJBFJz.3L1@usenet.ucs.indiana.edu> <1994Jan10.184623.16915@news.csuohio.edu> NNTP-Posting-Host: mnementh.cs.mcgill.ca In article <1994Jan10.184623.16915@news.csuohio.edu>, Steve Ratliff <stever@csuohio.edu> wrote: > > Be warned that the binary and source packages of top on >FreeBSD.cdrom.com currently have a rather substantial memory leak. > Top will grow in size about 30-40k every time that a new process >is started or exits. So don't run top for extended periods of time, >especially on a very busy system. Top will hang your system after it >gets to big. On my not very busy system, it locks the system up after >it has been running for about 24 hours. > I do not know if this applies to the NetBSD available source as well. >There doesn't seem to be any problem if you only run top for several >minutes at a time. You can actually use top itself to watch the memory >leak in action. :) the only problem i've had with top under netbsd is that it seg faults extremely frequently when the system is doing sommething relatively intense like a compile [even short term stuff]. no idea what the problem is. a half-hearted attempt with gdb didn't help, and it hasn't bothered me enough since then to stop using it. i left it running yesterday for about 6 hours under light system use, and it never exceed 700k or something like that. mar c'em. -- ----------------------------------------------------------------------------- Marc Wandschneider Seattle, WA Barney the Dinosaur sings! You faint... Barney sings! Barney sings! --More-- You Die... --More--