Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!sdd.hp.com!vixen.cso.uiuc.edu!howland.reston.ans.net!xlink.net!fauern!cs.tu-berlin.de!wosch
From: wosch@cs.tu-berlin.de (Wolfram Schneider)
Newsgroups: comp.os.386bsd.apps
Subject: Re: top-3.2 memory leak (Re: m_*bsd.c for top 3.0?)
Date: 25 Oct 1993 19:14:22 GMT
Organization: Technische Universitaet Berlin, Deutschland
Lines: 16
Message-ID: <2ah8ih$dud@news.cs.tu-berlin.de>
References: <29g3i2$o4q@homer.cs.mcgill.ca> <CEzt2r.1BF@luva.stgt.sub.org>
<ASAMI.93Oct22220018@forgery.cs.berkeley.edu>
NNTP-Posting-Host: pound.cs.tu-berlin.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
In-reply-to: asami@cs.berkeley.edu's message of 22 Oct 93 22:00:18
In article <ASAMI.93Oct22220018@forgery.cs.berkeley.edu> asami@cs.berkeley.edu (Satoshi ASAMI) writes:
Great, I uncommented it and now top runs happily as ever. However, I
still have a problem (which existed in top-3.0 I got from agate's
unsupported/from-ref directory too)---top seems to have a memory leak.
It was about 400k when it started, and now (after running for about
three hours), it stands at 1.4 megs. It grows much slower than
top-3.0, though.
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
^^^^^^^^^^^
Wolfram