🚀 go-pugleaf

Hello,
     I have been having difficulties with modules that I have written 
crashing with "exhausted shared memory" errors.  This can be as simple as 
two ReadLat's connected as inputs to a module that:
     creates internally a new lattice to duplicate (in shape/size) one   
       of the input lattices
     create a lattice four times larger than the other input lattice (it is
       a "4 vector" of the "1 vector" input lattice
     using the two input lattices values are copied into the "4 vector"
       output lattice
     the internal lattice (1st step above) is dereferenced:  i.e.:
       cxDataRefDec(lat);
     nothing else is going on as far as data allocation/deallocation is
       concerned

     With two lattices of about 1.5MB (and having a .explorerrc file in my 
home directory containing: arenasize 40mb) the above works several times, 
then (at a random execution) dies with the shared memory exhausted error.

     A related question: some of my modules need global data.  I create 
lattices and then use cxDataRefInc(lat) on them.  When I need to resize 
them, I call cxDataRefDec(lat) and lat = cxLatNew(...).  Does this cause 
the unwanted lattices to be discarded and reclaimed by explorer???
    Any help would be greatly appreciated...
-Joseph
pecquet@mps.ohio-state.edu
pecquet@ohstpy.bitnet