*BSD News Article 22744


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!isolar!isolar!not-for-mail
From: earle@isolar.Tujunga.CA.US (Greg Earle)
Newsgroups: comp.os.386bsd.apps
Subject: Re: top-3.2 memory leak (Re: m_*bsd.c for top 3.0?)
Followup-To: comp.os.386bsd.apps
Date: 24 Oct 1993 15:23:21 -0700
Organization: Personal Usenet site, Tujunga, CA USA
Lines: 36
Message-ID: <2aev8p$2io@isolar.Tujunga.CA.US>
References: <29g3i2$o4q@homer.cs.mcgill.ca> <ASAMI.93Oct22220018@forgery.cs.berkeley.edu> <2ad2ti$8n@vixen.cso.uiuc.edu> <g89r4222.751465624@kudu>
NNTP-Posting-Host: isolar.tujunga.ca.us
Summary: Tell the author

In article <g89r4222.751465624@kudu>,
Geoff Rehmet <g89r4222@kudu.ru.ac.za> wrote:
>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.
>
>--
>===========================csgr@alpha.ru.ac.za================================
> Geoff Rehmet, Parallel Processing Group, |  ____   _ o         /\
> Computer Science Department,             | ___  _-\_<,        /\/\/\
> Rhodes University, RSA.                  |     (*)/'(*)    /\/\/\/\/\

And *of course* all of you are telling the author, William LeFebvre
(phil@pex.EECS.NWU.EDU), about this so he can see if there is a problem/fix,
right?

-- 
- Greg Earle
  Phone: (818) 353-8695			FAX: (818) 353-1877 [Call # again if
  Internet: earle@isolar.Tujunga.CA.US			     you get data tone]
  UUCP: isolar!earle@elroy.JPL.NASA.GOV a.k.a. ...!elroy!isolar!earle