<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ExportCAD Memory Leak in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/exportcad-memory-leak/m-p/40143#M3203</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Did you figure this out?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 15 Oct 2011 16:05:05 GMT</pubDate>
    <dc:creator>RobertEhrman</dc:creator>
    <dc:date>2011-10-15T16:05:05Z</dc:date>
    <item>
      <title>ExportCAD Memory Leak</title>
      <link>https://community.esri.com/t5/python-questions/exportcad-memory-leak/m-p/40142#M3202</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Anyone have ideas on how to manage memory leaks from the ExportCAD_conversion tool? I am currently using the Delete_management tool to clear "in_memory" and also using del to delete the variable reference. I am looping through feature classes and appending them to a DWG with a seed file, I have overwriteoutput set to true as well.&amp;nbsp; Each iteration of the loop increases the memory by about .7GB until my script crashes at around 3.5GB. Its not an input format issue because i standardize everything before it get passed to the tool and doesn't crash on a certain fc consistently.&amp;nbsp; I have tried it in the ArcMap python window, pythonwin and pyscripter.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;After looking at the results tab when running the tool in the ArcMap python window, I notice that 2 export messages are listed stating; "Exporting *feature_class* to CAD" and "exporting to *CAD*.dwg" My thoughts are that the tool first exports the fc to "CAD" somehow in memory and I just not have been able to figure out how to clear it.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any ideas/help would be appreciated.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Jul 2011 18:45:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/exportcad-memory-leak/m-p/40142#M3202</guid>
      <dc:creator>DrewThompson1</dc:creator>
      <dc:date>2011-07-12T18:45:55Z</dc:date>
    </item>
    <item>
      <title>Re: ExportCAD Memory Leak</title>
      <link>https://community.esri.com/t5/python-questions/exportcad-memory-leak/m-p/40143#M3203</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Did you figure this out?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Oct 2011 16:05:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/exportcad-memory-leak/m-p/40143#M3203</guid>
      <dc:creator>RobertEhrman</dc:creator>
      <dc:date>2011-10-15T16:05:05Z</dc:date>
    </item>
    <item>
      <title>Re: ExportCAD Memory Leak</title>
      <link>https://community.esri.com/t5/python-questions/exportcad-memory-leak/m-p/40144#M3204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This bug has been logged by ESRI, search for the ID NIM071017. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;A work around we came up with was to create a temp dataset and create CAD formatted feature classes there. Once all the feature classes we need are in the temp dataset, we would set the workspace to that dataset, get a list of the feature classes, and use that list as the first input to the ExportCAD tool. Its still not ideal and I hate creating and saving intermediate data but it works. Hopefully that helps.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2011 14:49:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/exportcad-memory-leak/m-p/40144#M3204</guid>
      <dc:creator>DrewThompson1</dc:creator>
      <dc:date>2011-10-17T14:49:15Z</dc:date>
    </item>
  </channel>
</rss>

