Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!olivea!tymix!altair!jdresser
From: jdresser@altair.uucp (Jay Dresser)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Memory Protection!
Message-ID: <3762@tymix.UUCP>
Date: 29 Aug 90 22:45:14 GMT
References: <1145.26bd4989@waikato.ac.nz> <1410050@hpcvca.CV.HP.COM> <6423@sugar.hackercorp.com>
Sender: usenet@tymix.UUCP
Reply-To: jdresser@altair.Tymnet.com (Jay Dresser)
Organization: BT Tymnet, Inc. / San Jose, CA
Lines: 13

My solution to lost memory was rather straightforward.  I allocate
memory through my routines which alloc from chunks I get from
AllocEntry.  I then append the MemEntry to the list maintained in the
Task structure.  This memory is automatically freed by the system when
the task exits.  Thus no more lost memory.  This seems to me the way it
was meant to be.

This I wrote after implementing a more general cleanup system that
keeps track of alloced memory, open files, open libraries, or anything
else that needs to be undone when exiting.  I never have any hanging
anything.

Jay