home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!sgrenander@NASAMAIL.JPL.NASA.GOV
- From: sgrenander@NASAMAIL.JPL.NASA.GOV (Sven Grenander)
- Newsgroups: comp.sys.mac.system
- Subject: Re: 7.x.x Finder Heap Allocation ?
- Message-ID: <1992Sep2.223818.8558@elroy.jpl.nasa.gov>
- Date: 2 Sep 92 22:38:18 GMT
- References: <1992Sep1.164852.29038@elroy.jpl.nasa.gov> <1992Sep2.191821.22486@newsgate.sps.mot.com>
- Sender: news@elroy.jpl.nasa.gov (Usenet)
- Organization: Jet Propulsion Laboratory
- Lines: 33
- Nntp-Posting-Host: mac4.jpl.nasa.gov
-
- In article <1992Sep2.191821.22486@newsgate.sps.mot.com>, gpb@gpb-mac. (greg berryman ) writes:
- >
- > sgrenander@NASAMAIL.JPL.NASA.GOV (Sven Grenander) writes:
- ......
- > :
- > : What SWATCH (a pretty neat little app) showed was that the finder heap is the problem.
- > : It is fixed at around 263K (or close to it, maybe it varies from machine to machine ?)
- > : and sure enough, its free space which is usually around a measly 4K sometimes sinks
- > : to 500 bytes, followed by the OOM message.
- .......
- > : So, the question is how to increase the finder heap allocation to
- > : make the problem less likely to occur. I tried ResEditing the Finder to increase the
- > : allocation, but the system will not boot with the edited copy.
- .........
- > I have had the same problem on a number of machines along with assorted bombs
- > due to "bad f-line instruction" errors. I used ResEdit to change Finder's
- > memory allocation up to 358400 in the SIZE=-1 resource. The problems went
- > away afterwords.
- .......
- >
- > AS ALWAYS WITH RESEDIT DO THIS AT YOUR OWN RISK!
- >
- > --
- > Greg Berryman gpb@gpb-mac.sps.mot.com
- > Motorola Inc. Austin Texas
- >
- >
-
- Quite right. I must have messed up the Finder the first time I tried ResEditing
- it (as was also pointed out in private mailings). ResEdit did do the job and my Mac
- is much more comfortable !
-
- -Sven
-