Reset local memory in ArcMap 10

Question

I often am unable to delete files due to a lock or need to reset the data frame coordinate system. Very often starting a new session of Arc will allow certain geoprocessing or data management tasks to run effectively. What solutions exist to reset the local memory usage in ArcMap 10 other than closing and starting a new session? For the Python programmers out there, is there a way to add code to scripts that clears local memory before or after running geoprocessing tasks?

• blah238: Can you be more specific about what you are having trouble with? Better to tackle the issues individually rather than take a hammer to it.
• Aaron: I'm looking for more of a hammer approach on this one. It seems that I often resort to starting a new session of Arc as part of my geoprocessing troubleshooting routine--very often this last resort works! This leads me to believe that local memory storage may be the underlying issue to many unusual geoprocessing quirks (e.g. the failed tasks that shoot back a generic error message).

Answer 1

Geoprocessing is set to run in two ways: foreground and background. Someone who has more ezperience then I do can comment on the specific nuances of either setting in relation to memory leakage.

However, when running geoprocessing tools, many of which store temporary data in memory and it could be the tool itself that is causing the memory to reach capacity and errors to occur.

I can address the arcpy issues as Ive been tackling them myself lately. Its important to use the in_memory workspace when possible to speed up processing but always remember to delete temporary data from that workspace if its not needed anymore using a "del object" statement or using thr Delete_management() function.

Inside arcmap, a failed script or tool can be caused by memory leaks not alllowing the tool to finish its job. Sometimes the input format of the data makes a large difference in processing costs ( excel table vs csv, vs dbf). What tools are failing on you? There are known issues with ones like xy to line.

More information would be helpful. Please update with specific tasks that are causing you trouble.

• Aaron: +1 This is really helpful, thanks hhart. Regarding specific problem tasks, multi-ring buffering large polygon files immediately comes to mind as a real troublemaker, yet manageable in a fresh work session.
• blah238: Specifically regarding the in_memory workspace, the only way to clear it out is with Delete_management; del object will not do anything.
• blah238: I would also be careful before using the term memory leak as that has a very specific technical meaning; I would suggest "memory consumption" instead.
• blah238: Or just "memory usage". Just because an application uses a lot of memory doesn't mean it is leaking memory.