Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!hao!husc6!cca!mirror!rayssd!brunix!nancy!omh
From: omh@nancy (Owen M. Hartnett)
Newsgroups: comp.sys.mac
Subject: Re: LightSpeed Pascal bug? (Or perhaps SigmaEdit bug)
Message-ID: <23207@brunix.UUCP>
Date: 28 Feb 88 05:06:30 GMT
References: <1199@ucdavis.ucdavis.edu>
Sender: root@brunix.UUCP
Reply-To: omh@nancy.UUCP (Owen M. Hartnett)
Organization: Brown University Computer Science Dept.
Lines: 62

In article <1199@ucdavis.ucdavis.edu> uucp@ucdavis.ucdavis.edu (uucp) writes:
>I have discovered a problem while using LightSpeed Pascal, I hope
>someone can shed some light on it.
>
>I have an open project and have just finished building and linking
>it.  Total project sized is < 30000 bytes.  I try to "Go" to the
>compiled application and I get an error that says something to the
>effect that "Not enough memory to run...Perhaps you have an open
>desk accessory..."
>
>Like I said, the project is small, and also I tried closing all open
>text windows (by choosing close from menu, not clicking the close
>box).  By the way, no desk accessories are open when this occurs.
>HOWEVER...I notice that the problem seems to occur after I use 
>SigmaEdit to edit a source file (sorry Think, but the LSP editor is
>too slow).  I close SigmaEdit, compile, try to run, and get the
>error message.

This is not just a problem with SigmaEdit, but with any desk accessory
which allocates any appreciable space  (Even some DAs which use only a little
memory will cause it if called often enough from the environment).

As a matter of fact, once you get this message there's no way out except
returning to the finder.

I talked to one of the original authors about it at a BCS Techgroup meeting
last year.  He indicated that he would look at it seriously for the next
release (whenever that may be). (I heard a rumor, however, that he is no
longer with Think.)

Anyway, you can reduce the number of times that you'll encounter it by
watching your memory allocations (in the Run Options menu).

One hint I got from the original author was not to set the stack size above
31K.  (There's really no reason that you should, that's a lot of stack.)
It seems there was a bug which appeared at stack size 32K or greater.  I don't
know if it's been fixed in the newest release.

I run with a heap size of 200K for a fairly medium size program and most 
desk accessories run OK.  But if you open up a text editor DA with it's
ensuing memory (like a big TE record), you're bound to hit this wall.

I don't know if it's the DA that isn't cleaning up after itself, or that LSP
can't detect the clean-up.

Certain DA

Certain DAs will cause this error every time they're run.  I ran out of memory
on a Mac II with 2MB Ram trying to run ResPeek. Also, the MacMan Da that was
posted a while back allocates a lot of non-relocatable blocks which of course
cause LSP to run out of room very quickly.

-Owen

Owen Hartnett
Brown University Computer Science

omh@cs.brown.edu.CSNET 
omh%cs.brown.edu
{ihnp4,allegra}!brunix!omh

"Don't wait up for me tonight because I won't be home for a month."
			-W.C. Fields