🚀 go-pugleaf

After running out of memory a few times, I watched the process sizes
with the "top" command to see which modules in my map were taking up
more memory.

Each time I looped through my map, Render got a little bigger. My map
repeatedly sends geometry to the Render module via the same output-input
wire. Render is smart enough to delete the old geometry from the screen,
but not apparently from memory. Gradually it just keeps growing until
I'm paging so hard I can't even CNTRL-C out of the program, and usually
end up at the Reset button.

This looks like a job for an SGI person with access to the Render source.
Are you there? Can we fix this? 

I hope either 1) I can get this fixed without having to wait for 2.0, or
              2) It's fixed in 2.0 and 2.0 is in the mail right now.

Any suggestions? Any way I can work around it? Thanks

-- 
----------------------------------------------------------------------
Scott Ferguson                        Exxon Research & Engineering Co.
Project Engineer                      New Jersey
----------------------------------------------------------------------
"Always bark at a dog."