Memory allocation after deleting big waves
Thu, 12/12/2013 - 07:08 am
According to the Mac activity monitor, Igor then still occupies 800-900 MB of memory. When loading a new data set of this size into a 3D wave this results in an "out of memory" error, as the loading procedure contains a Duplicate command. Restarting Igor is the only option. This behaviour seems to be rather random, sometimes it works, sometimes not.
Is there any work-around for this? My goal is to do batch processing on such data sets which requires sequential killing and loading.