Path: utzoo!attcan!uunet!husc6!cmcl2!nrl-cmf!mailrus!tut.cis.ohio-state.edu!uwmcsd1!ig!agate!saturn!ucscb.UCSC.EDU!alibaba From: alibaba@ucscb.UCSC.EDU (Alexander M. Rosenberg) Newsgroups: comp.sys.mac.programmer Subject: Re: StartUpScreens Eats Memory!? Summary: Uh, Oh, Chongo!!! Message-ID: <3243@saturn.ucsc.edu> Date: 11 May 88 01:43:26 GMT References: <22188@tis.llnl.gov> <9488@apple.Apple.Com> <1419@claris.UUCP> Sender: usenet@saturn.ucsc.edu Reply-To: alibaba@ucscb.UCSC.EDU (Alexander M. Rosenberg) Organization: Univ. of California at Santa Cruz Hacker's Anonymous Lines: 19 I heard about this problem as far back as last July. When a PICT file with PICT id=0 is loaded (this does not occur for MacPaint startupscreens), the memory on the heap is not recovered, and you lose big time. The trick here is in determining which part of the Mac system does the loading of the StartupScreen. Since the boot blocks on disks have the filename to load in them, we must assume that the startupscreen loader is contained in the boot blocks of the startup drive. Since Apple apparently already knows about this bug (it was a compuserve topic a while back...) they will probably (hopefully???) have it fixed in System 6.0. It probably isn't very difficult to fix, but low on the prority list, as StartUpScreens are a frill. I am not totally sure of the fix as I have not looked at the loader code. ------------------------------------------------------------------------------- - Alexander M. Rosenberg - INTERNET: alibaba@ucscb.ucsc.edu - Yoyodyne - - Crown College, UCSC - UUCP:...!ucbvax!ucscc!ucscb!alibaba- Propulsion - - Santa Cruz, CA 95064 - BITNET:alibaba%ucscb@ucscc.BITNET - Systems - - (408) 426-8869 - Disclaimer: Nobody is my employer - :-) - - - so nobody cares what I say. - -