Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!lll-winken!snll-arpagw!paolucci
From: paolucci@snll-arpagw.UUCP (Sam Paolucci)
Newsgroups: comp.sys.amiga.tech
Subject: Re: CloseFonts() problems
Message-ID: <26@snll-arpagw.UUCP>
Date: 3 Jan 89 03:25:00 GMT
References: <3599@tekig5.PEN.TEK.COM> <10097@well.UUCP> <YXienJy00Vsf0AHTAo@andrew.cmu.edu> <14355@oberon.USC.EDU> <3226@amiga.UUCP> <14370@oberon.USC.EDU> <10191@well.UUCP>
Reply-To: paolucci@snll-arpagw.UUCP (Sam Paolucci)
Organization: Sandia National Labs, Livermore, CA
Lines: 22

In article <10191@well.UUCP> ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes:
->	Checking to see if everything get returned can be a bit of a pain,
->particularly if you're working out of VD0: (which is not to slander VD0:).
->My test cycle is:  avail, <program>, avail.  If the program opened
->previously unopened libraries, then I do another <program>,avail cycle and
->check the numbers.  In VD0:, this can be a problem, because it likes to free
->up memory "every so often".  Thus, I often find myself saying "dir >NIL: :
->OPT A" to try and make it happen more often so that the avail numbers don't
->say I have more free memory that I started with.

Doesn't memory get freed if you run CleanRamDisk?  I believe that this
program was provided with VD0: specifically for the purpose of freeing
up the memory.

->Leo L. Schwab -- The Guy in The Cape	INET: well!ewhac@ucbvax.Berkeley.EDU


-- 
					-+= SAM =+-
"the best things in life are free"

				ARPA: paolucci@snll-arpagw.llnl.gov