Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!rex!ames!sheba.arc.nasa.gov!schoch
From: schoch@sheba.arc.nasa.gov (Steve Schoch)
Newsgroups: comp.windows.x
Subject: Re: Server Does Not Free Widget Resources
Keywords: widget resources, memory leak
Message-ID: <1990Dec7.212838.28921@news.arc.nasa.gov>
Date: 7 Dec 90 21:28:38 GMT
References: <593@censun1.UUCP> <1990Dec7.175818.12931@thyme.jpl.nasa.gov>
Sender: usenet@news.arc.nasa.gov (USENET Administration)
Reply-To: schoch@trident.arc.nasa.gov (Steve Schoch)
Organization: NASA Ames Research Center, Moffett Field, CA
Lines: 14

In article <1990Dec7.175818.12931@thyme.jpl.nasa.gov>, kaleb@thyme.jpl.nasa.gov (Kaleb Keithley	) writes:
|> You will never see the server process size shrink or reduce.  That's
|> just how malloc/free work.

That's what I would have said too, except that he said the problem happened
on NCD X Terminal servers also.  NCD terminals don't run Unix, or a multi-
user OS in general so I would think they would use a different implementation
of malloc/free (The UNIX version of free makes the memory available to
future calls to malloc() but does not give the memory back to the kernel.)

My question to tae@censun1.UUCP is:  "How do you know how much server memory
an NCD terminal is using?"

	Steve