Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!bu.edu!m2c!umvlsi!dime!krovetz
From: krovetz@cs.umass.edu (Bob Krovetz)
Newsgroups: comp.sys.ti.explorer
Subject: swap space problem
Message-ID: <25493@dime.cs.umass.edu>
Date: 23 Jan 91 10:31:21 GMT
Sender: news@dime.cs.umass.edu
Followup-To: comp.sys.ti.explorer
Organization: Computer and Information Science, University of Massachusetts, Amherst, MA
Lines: 22

I'm using a micro-explorer, running release 6.31, and I'm having a problem with
my swap space running low.  The storage continues to accumulate as I use the
system, but I'm not sure what's taking up so much space.  I start out with a
load band of about 60MB (I have a number of large data structures included
in it).  After I've used the system for several days (sometimes a week), I
find the dump size has increased to about 120MB, and I get messages about 
`swap space low'.  I did a (si:describe-all-areas) before I rebooted, and 
compared that with the results right after rebooting.  The areas that 
seemed to be causing the problem are: P-N-STRING, and PDL-AREA.  There
were also increases in WORKING-STORAGE and PERMANENT-STORAGE, but they
weren't as big a factor as the other two.  Does anyone have any suggestions
for how I can determine what is taking up this storage?  Is there any 
way to `layer' storage allocation - i.e., tell the system to allocate
all storage from now on in a separate layer, and then `pop the stack'
when the storage gets low?  I don't want to explicitly refer to areas
on each interaction; I just want to say something like `push storage area'
and `pop storage area'.

Thanks,
Bob

krovetz@cs.umass.edu