Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!orsvax1!pyrnj!caip!lll-crg!styx!nike!cad!ucbvax!jade!violet.berkeley.edu!csfred
From: csfred@violet.berkeley.edu.berkeley.edu (/violet_e/csfred)
Newsgroups: net.micro.mac
Subject: Memory Manager Bug?
Message-ID: <784@jade.BERKELEY.EDU>
Date: Thu, 5-Jun-86 14:41:46 EDT
Article-I.D.: jade.784
Posted: Thu Jun  5 14:41:46 1986
Date-Received: Sun, 8-Jun-86 03:46:26 EDT
Sender: usenet@jade.BERKELEY.EDU
Reply-To: csfred@violet.berkeley.edu.UUCP (Frederick A. Huxham)
Organization: University of California, Berkeley
Lines: 35

>>>[ from Dave, the President of Living VideoText ]
>>>
>>>2) There is a bug in the Apple ROMs - and we've trapped it - and fixed it.
>>>Version 1.3 will be available at no charge to registered users using Mac+
>>>just for the asking.
>>>
>>
>
>Altsys, makers of FONTastic (and the new Fontographer) are sending out a note
>with their Mac+ compatible releases, that states there is a memory management
>bug in the new ROMs.  The effect is that memory is not freed or reclaimed
>until the application quits.

I'd be really interested in reading exactly what the note says.  I called
Altsys to find out what it said, but the two people I talked to didn't 
know anything about the note.  

I'm currently writing a Postscript Interpreter for the Mac that makes
a LOT of calls to NewHandle, HLock, HUnlock, GetHandleSize, SetHandleSize,
and DisposHandle.  Memory is constantly being allocated and deallocated.

In writing the application, I've also spent quite a bit of time 
cruising around the heap in TMON to make sure handles are the right
size, are pointing at the right data, etc.  

I'd be pretty confident to say that on my MacPlus, memory is being
freed and reclaimed.

So if anyone has the note from Altsys, or knows specifically what the
memory management bug is, I'd love to hear about it.

Thanks,

Fred A. Huxham
Advanced Workstation Consultant - UCB