sonenbli@oxy.edu (Andrew D. Sonenblick) (01/09/90)
I just received my copy of Think C 4.0 and I am having significant
problems. Whenever I create a project while running MultiFinder, it will work
properly the first time, ie compile, run, return to Think C. If I make any
changes to it after that--edit my source code, add/remove MacTraps, oops, etc--
and try to rerun it, it compiles and then Think C reports out of memory errork
(even if I drastically shortened my source code!) I can't even quit--OUT OF
MEMORY!!! If I interrupt, return to the Finder, double click on the projectc--
(thus booting Think C) it opens and Bam! Out of Memory.s out of memory error
I am running on a Mac+ with 2.5 Megs--after an out of memory error, I can
switch to the Finder and check on C's partition via About the Finder... and of
its 700K, it's usually only half full. (My source code is only a few pages
long, doing only the minimum of an application.)r my out of memory error, I can
However, if I create my project without running MultiFinder, everythingf
works fine. Then I can boot up MultiFinder and as long as I don't Changees
MacTraps or oops (I can edit and recompile my source, and remove and add others)
things work. But I don't like this limitation and restriction of freedom.ing
Is this something that has happened to others or only to me? I am exper-
ienced in Think C and this behaviour occurs whether I am using object exten-ers)
sions and/or the TCL or not. Do I have a bum copy? I can think of no logical
reason for this behaviour (I even close all one of my windows like suggested
in the manual...) Anyone have any ideas, info, comments?y to me? I am exper-
Thanks for listening and responding... Ando: sonenbli@oxy.edu
it behave no differently when I do.) Any Ideas? Info? Comments? Help?olson@bootsie.UUCP (Eric Olson) (01/12/90)
In article <69286@tiger.oxy.edu> sonenbli@oxy.edu (Andrew D. Sonenblick) writes: > >and try to rerun it, it compiles and then Think C reports out of memory errork I am not sure about what I am about to say, except to say that it works for me. I don't know which things cause Think C's "Out of Memory" alert and which would cause some other memory error (i.e., I don't know which of these things will actually fix your problem-- try 'em all [in order]). 1. Change the application's partition size in the "Set Project Type" dialog. 2. Select "More Memory" in the "Edit" menu "Options..." dialog "Preferences" section. This slows down compiling and I don't know if it helps in your case, since I thought it was for temporary data. 2. Make Think C's partition size _smaller_, since it isn't all being used and maybe it's the application partition that can't be allocated. 3. Don't run the debugger, or decrease its partition size (I wouldn't make it smaller than the minimum though-- its tiny anyway). I have successfully compiled huge TCL things [Prepare()] on a 2.5 Meg Plus. By huge I mean that the Project file is about 1.3 Meg. -Eric -- Eric K. Olson olson@endor.harvard.edu harvard!endor!olson
daf@pacvax.UUCP (David A. Fagan) (01/12/90)
I've had the same problem, though I never associated it with MultiFinder. I seem to get it after debugging a project which crashes badly. I guess the project file gets corrupted somehow. I just throw it out & remake it. Dave Fagan Pacer Software, Inc. uunet!pacvax!daf