Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!amdahl!uunet!garfield!john13
From: john13@garfield.MUN.EDU (John Russell)
Newsgroups: comp.sys.amiga.tech
Subject: Expunge problems (was Re: CloseFonts() problems)
Summary: problem with expunge
Message-ID: <5058@garfield.MUN.EDU>
Date: 31 Dec 88 17:32:48 GMT
References: <3599@tekig5.PEN.TEK.COM> <10097@well.UUCP> <YXienJy00Vsf0AHTAo@andrew.cmu.edu> <14355@oberon.USC.EDU> <3226@amiga.UUCP>
Reply-To: john13@garfield.UUCP (John Russell)
Distribution: na
Organization: Memorial University of Newfoundland
Lines: 21

In article <3226@amiga.UUCP> jimm@cloyd.UUCP (Jim Mackraz) writes:
>If you NEED the memory, won't you get
>it when you try to allocate it?  If you need a large chunk of memory, won't
>an expunge happen when you try to get it?
>
>Problems I'm aware of include:
...

There's also the problem that when loading a large executable, fragmentation
caused by unused fonts, libraries, and devices may mean it fails with
"not enough memory". A flushlibs will cure the problem, but it would be
better for the loadseg (or whatever the dos routine at the root of the
problem) actually tried an AllocMem -- I can only suppose it examines the
memlist looking for a large enough contiguous block, but never does anything
that would cause an expunge.

John
-- 
"If you steal all money, kids not be able to BUY TOYS!"
			-- Saturday morning cartoon character explaining
			   why theft is bad