Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!gatech!udel!new
From: new@udel.EDU (Darren New)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Flushing handlers out of memory.
Message-ID: <19912@louie.udel.EDU>
Date: 17 Jul 89 19:54:07 GMT
References: <59256@linus.UUCP> <18551@usc.edu> <4118@amiga.UUCP>
Sender: usenet@udel.EDU
Reply-To: new@udel.EDU (Darren New)
Organization: University of Delaware
Lines: 11


Note that if you start workbench with debug (loadwb -debug) then the
debug menu to the right of the special menu will have a flushlibs
that tries to allocate all the memory. If you want to expunge your
library every time you test it, simply call Expunge just after
you OpenLibrary. When the use count goes to zero, your library should check
and deallocate itself. When Exec runs out of memory, it seems to call
expunge on all the libaries (causing them to flush if zero count)
and then retry. Of course, I don't know if this works for handlers,
but all this stuff is already there for you in the case of libaries.
			    -- Darren