Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Flushing handlers out of memory.
Message-ID: <7370@cbmvax.UUCP>
Date: 20 Jul 89 06:07:57 GMT
References: <59256@linus.UUCP> <1110@sas.UUCP>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 17

In article <1110@sas.UUCP> walker@sas.UUCP (Doug Walker) writes:
>does exactly that.  It doesn't unload the handler code, though, so it's only
>useful during program development.  I suggest putting a back door msgport in
>your handler that lets you force it to give up its resources (as much as possible)
>and die.

	Don't ever let the process die.  Someone may have DeviceProc'ed you,
and may send you a packet at any time.  At absolute most, free up resources
and all code but a fragment that waits on the pr_MsgPort and replies all
messages with errors.

	1.4 will address usage counts for handlers.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Common phrase heard at Amiga Devcon '89: "It's in there!"