Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!spool.mu.edu!bloom-beacon.mit.edu!mcrcim.mcgill.edu!homer.cs.mcgill.ca!storm
From: storm@cs.mcgill.ca (Marc WANDSCHNEIDER)
Newsgroups: comp.os.386bsd.apps
Subject: Re: top-3.2 memory leak (Re: m_*bsd.c for top 3.0?)
Date: 26 Oct 1993 14:27:47 GMT
Organization: SOCS, McGill University, Montreal, Canada
Lines: 31
Message-ID: <2ajc53$rvj@homer.cs.mcgill.ca>
References: <29g3i2$o4q@homer.cs.mcgill.ca> <CEzt2r.1BF@luva.stgt.sub.org> <2ah8ih$dud@news.cs.tu-berlin.de> <2aj272$lnv@netbsd08.dn.itg.telecom.com.au>
NNTP-Posting-Host: mnementh.cs.mcgill.ca
In article <2aj272$lnv@netbsd08.dn.itg.telecom.com.au>,
Terry Dwyer netbsd08 619 491 5161 <tdwyer@netbsd08.dn.itg.telecom.com.au> wrote:
>Wolfram Schneider (wosch@cs.tu-berlin.de) wrote:
>
>{other stuff deleted}
>
>: I have no problems with top-3.2. I use the orginal top and a patch for
>: swap usage.
>
>: Memory: Free: 180K Act: 1196K Inact: 220K Wired: 1268K Swap: 3344K
>: ^^^^^^^^^^^
On the topic of Top problems:
Whenever I am compiling XFree86, and I start to run top, it seg
faults, especially if I hit space a few times to do a non-default
refresh....
It seems as though when there are a lot of processes changing
rapidly, something breaks.
I'll be looking into it more later this week.
Marc 'em.
--
-----------------------------------------------------------------------------
Marc Wandschneider Seattle, WA
Barney the Dinosaur sings! You faint... Barney sings! Barney sings! --More--
You Die... --More--