Path: utzoo!attcan!uunet!seismo!ukma!tut.cis.ohio-state.edu!francis From: francis@tut.cis.ohio-state.edu (RD Francis) Newsgroups: comp.sys.mac.misc Subject: Re: Edit 2.1: In a heap of trouble? Message-ID: <81287@tut.cis.ohio-state.edu> Date: 8 Jun 90 12:47:21 GMT References: <10566@spool.cs.wisc.edu> Reply-To: RD Francis Organization: Ohio State University Computer and Information Science Lines: 35 In article <10566@spool.cs.wisc.edu> tonyrich@titanic.cs.wisc.edu (Anthony Rich) writes: >THE NEW SUSPECT. >With some further experimentation I think I now see the problem. (I'm not >all that familiar with Mac internals, so somebody please correct me if I'm >wrong.) As I understand it, inits and cdevs occupy an an area of memory >called the system heap; apparently it's an area of limited size. Edit 2.1 >appears to start crashing when the addition of inits/cdevs reduces the >amount of free space in the system heap below some threshold. It doesn't >seem to matter which inits/cdevs are in there; it's the amount of system >heap that's left over for Edit to use that matters. And apparently just >"disabling" the inits/cdevs doesn't do the trick, you have to actually >remove them from the System folder. > >I did a "Get Info" on Edit and saw that its suggested and actual application >memory size (not the same thing as the system heap size) was 224K; hoping for >the best, I tried increasing that to 512K, and for a while I thought that >fixed things, but it didn't; I still got crashes. Quick question: are you running under Multi-Finder? If so, then you haven't found a solution to your problem. Under Multi-Finder, programs grab a chunk of memory and keep it. In general, if the memory needed isn't available, the program won't launch. Finally, the system heap is separate, so it wouldn't be having an effect on Edit However, if you are not using Multi-Finder, then applications, when launched grab all available space. If all available space is less than that 224K recommended figure, Edit may not complain.However, as soon as it starts wanting more memory, it may well just up and die. Increasing the system heap in these circumstances, will only reduce the amount of available memory even more. Check how much memory isn't taken up by the System in the About Finder dialog; that should help. -- R David Francis francis@cis.ohio-state.edu