Is there any way to debug geoprocessor memory leaks?
I am scripting pyramid generation for a raster catalog (more than one million datasets) in 9.3.1 and after 6000 raster datasets i'm using 620mb of ram, after 6500 raster datasets i'm using 667mb, and when it hits 2gb ram usage it crashes since its a 32bit app.
Any ideas? My catalog is in a filegeodatabase as an unmanaged raster catalog.