Return to BSD News archive
Newsgroups: comp.os.386bsd.apps Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!ee.und.ac.za!hippo.ru.ac.za!kudu!g89r4222 From: g89r4222@kudu.ru.ac.za (Geoff Rehmet) Subject: Re: top-3.2 memory leak (Re: m_*bsd.c for top 3.0?) Message-ID: <g89r4222.751465624@kudu> Sender: news@hippo.ru.ac.za (Usenet News Admin) Organization: Rhodes University, Grahamstown, South Africa References: <29g3i2$o4q@homer.cs.mcgill.ca> <CEzt2r.1BF@luva.stgt.sub.org> <ASAMI.93Oct22220018@forgery.cs.berkeley.edu> <2ad2ti$8n@vixen.cso.uiuc.edu> Date: Sun, 24 Oct 1993 12:27:04 GMT Lines: 27 In <2ad2ti$8n@vixen.cso.uiuc.edu> rkb55989@uxa.cso.uiuc.edu (Rafal Boni) writes: >asami@cs.berkeley.edu (Satoshi ASAMI) writes: >>top-3.0 used to kill itself after a few hours---I haven't witnessed >>what happens to top-3.2, but my machine crashed a couple of days ago >>(with a long-running top of 4 megs or so). I don't know if it's >>because of top, but I was away and nothing but xscreensaver and top >>was running (actively) on the machine. This machine hasn't crashed >>for more than a week until then. > I have seem this not only on BSD, but on a bunch of systems, > many of them being the university *NIX machines.... On the > sequent symmetry that I have all my mail routed to, it grows > much faster then on my 486 box... [But then again, the symmetry > has gonzo memory, so it would probably take years to crash ;>] I have just compiled top-3.3 and it also has a problem with an almightly huge memory leak. Geoff. -- ===========================csgr@alpha.ru.ac.za================================ Geoff Rehmet, Parallel Processing Group, | ____ _ o /\ Computer Science Department, | ___ _-\_<, /\/\/\ Rhodes University, RSA. | (*)/'(*) /\/\/\/\/\