> 1642 ajack 30 15 454M 201M 154M R N 1.5 80.7 34:08 0 python > > do we have a memory leak somewhere?
Python is a hard language to debug, at least for me & especially at the size of things that a Gump workspace generates. Any Python folks know how to get inside this thing? Gumpy internals are getting a little out of control, but nothing that ought cause this. If I run a copy w/ --debug maybe I can see where it was at when it grew. regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]