Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!husc6!m2c!applix!scott
From: scott@applix.UUCP (Scott Evernden)
Newsgroups: comp.sys.amiga
Subject: Re: SBProlog's use of chip memory.
Message-ID: <937@applix.UUCP>
Date: 25 Mar 89 22:09:26 GMT
References: <4704@charon.unm.edu>
Reply-To: scott@applix.UUCP (Scott Evernden)
Organization: APPLiX Inc., Westboro MA
Lines: 28

In article <4704@charon.unm.edu> cs5041ai@ariel.unm.edu () writes:
>I have been using SBProlog the past few days and I am irritated by the fact
>that it uses up all my chip memory.  I have an A1000 with 2.5 meg of memory,
>so there is plenty of fast memory for it to use.  However is uses up about
>450k of precious chip memory, and I can't see any reason for it.

I just fired up SBProlog to check this.  Before I started memory looked like:

FAST memory: 1100872
CHIP memory: 359376
Total  Free: 1460248

With SBProlog 2.3.2 running, it's now:

FAST memory: 159176
CHIP memory: 359376
Total  Free: 518552

So, I can't repeat your problem.  However, SBProlog does allocate 2 rather
huge blocks of memory of like 450K and 300K each (if my memory is correct).
If your FAST memory if badly fragmented enough, then the allocation
may wind up coming from CHIP if only to return the contiguous 450K block.

There is no immediately obvious way to change the way SBProlog manages its
memory,  Of course, you are free to hack away.  I would try running
SBProlog on a freshly booted machine to see if the problem goes away.

-scott