🚀 go-pugleaf

In a network of mine, I'm repeatedly running a loop that sequences
through time, interpolates a time slice, renders, then records to video.

After about 200 or so frames (time slices), the machine bogs down, and
starts thrashing. The order of execution gets strange, things slow
down severely, etc.

I assume I must have filled up available memory some how and I've started
paging heavily.

One of my modules creates a new lattice with cxLatNew, and returns a pointer
to the lattice which goes to the module output port. I assumed that the
Explorer executive would automatically free this lattice for me. Is that 
incorrect? Should I be keeping this pointer as a global variable, and doing
a cxDataFree on it before creating new lattices?

Thanks
-- 
----------------------------------------------------------------------
Scott Ferguson                        Exxon Research & Engineering Co.
Project Engineer                      New Jersey
----------------------------------------------------------------------
"Remember, if you win the rat race, you're still a rat."