Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!nosc!crash!alen
From: alen@crash.cts.com (Alen Shapiro)
Newsgroups: comp.sys.mac.system
Subject: Re: Finder memory problems
Message-ID: <5996@crash.cts.com>
Date: 30 Nov 90 15:53:17 GMT
References: <12570.9011281439@s4.sys.uea.ac.uk>
Organization: Crash TimeSharing, El Cajon, CA
Lines: 24

In <12570.9011281439@s4.sys.uea.ac.uk> jrk@information-systems.east-anglia.ac.uk (Richard Kennaway CMP RA) writes:

>Correction to my earlier message: I have now observed the behaviour
>without having printed anything since booting.  All I'd done was run
>Telnet, Word 4, and mount and dismount an AUFS volume.  Then I couldnt
>open MacDraw II, although there should have been room.  I still cant
>make it happen reproducibly though.

I've run across a similar problem - here's an experiment to try...

Try the above sequence a) with many volumes mounted and b) with
few volumes mounted. If the problem gets worse/better (in that order)
try increasing the buffer size allocated to finder using Layout 1.9
(or more recent if one is available). This buffer size is NOT the
"File:Get-Info" startup memory allocation but some internal
finder allocation that layout can change. I've noticed that this
internal space affects file copying, application launching, system
reliability.....Apple please take note - it is not nice to have the
system crash during a file copy (from finder) just because internal
mount buffers are used up!!

--alen the Lisa Slayer (trying to turn a SPARC into a flame)
    alen%shappy.uucp@crash.cts.com (a mac+ uucp host - what a concept!!)
    alen@crash.cts.com