Subject: An example of top(1) bloat...
To: Port Mac 68K <port-mac68k@NetBSD.ORG>
From: Mason Loring Bliss <mason@acheron.middleboro.ma.us>
List: port-mac68k
Date: 12/23/1997 12:34:36
This seems like a lot of memory for top to be using... The odd bit is that
this never happened with the older top, under NetBSD/mac68k 1.2G, or maybe
just before that... Before the "swap change," anyway - circa June. (I'm
currently using the version of top(1) in our package system.)
I'm suspecting a memory leak in top(1), and I suppose I'll find an address
before too long to send a report to whomever it is that's working on
top(1), but I want to see if anyone else is experiencing this, before I
write.
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
9449 mason 36 4 1144K 420K run 53:37 1.38% 1.38% top
Here's memory usage from a fresh top(1) process which I just started:
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
5663 mason 36 4 212K 584K run 0:02 1.46% 1.38% top
Thanks in advance for clues. :)
--
Mason Loring Bliss...mason@acheron.middleboro.ma.us...www.webtrek.com/mason
"In the drowsy dark cave of the mind dreams build their nest with fragments
dropped from day's caravan."--Rabindranath Tagore...awake ? sleep : dream;