Here is a brief track of a couple of leaks.<br>
<br><br>{12783} normal block at 0x0D09DCC0, 52 bytes long.<br> Data: <D e f a u l t > 44 00 65 00 66 00 61 00 75 00 6C 00 74 00 20 00 <br>{12782} normal block at 0x0D09DC50, 52 bytes long.<br> Data: <R P J U R I D I > 52 00 50 00 4A 00 55 00 52 00 49 00 44 00 49 00 <br>
<br><br>These are two strings, allocated here:<br><br>Fdo\Unmanaged\Src\Fdo\Schema\FeatureClass.cpp:<br>FdoFeatureClass* FdoFeatureClass::Create(FdoString* name, FdoString* description)<br>{<br> return new FdoFeatureClass(name, description);<br>
}<br><br><br>Further down the callstack:<br><br>Utilities\Common\Src\FdoCommonSchemaUtil.cpp:<br>FdoFeatureClass * FdoCommonSchemaUtil::DeepCopyFdoFeatureClass(FdoFeatureClass * sourceClass, FdoCommonSchemaCopyContext * schemaContext)<br>
{<br> FdoPtr<FdoFeatureClass> newClass = FdoFeatureClass::Create(sourceClass->GetName(), sourceClass->GetDescription());<br> ....<br> FDO_SAFE_ADDREF(newClass.p);<br> return newClass;<br>}<br><br><br>d:\src\o\FDO\Utilities\Common\Src\FdoCommonSchemaUtil.cpp<br>
FdoClassDefinition * FdoCommonSchemaUtil::DeepCopyFdoClassDefinition(FdoClassDefinition * sourceClass, FdoCommonSchemaCopyContext * schemaContext)<br>{<br> newClass = DeepCopyFdoFeatureClass(static_cast<FdoFeatureClass*>(sourceClass), schemaContext);<br>
...<br> FDO_SAFE_ADDREF(newClass.p);<br> return newClass;<br>}<br><br><br>Providers\ArcSDE\Src\Provider\ArcSDEDescribeSchemaCommand.cpp:<br>void ArcSDEDescribeSchemaCommand::cloneClassDefinitions(FdoStringCollection* qFCNames, FdoFeatureSchemaCollection* retSchemaCol, FdoFeatureSchemaCollection* schemaCol):<br>
{<br> classes = retSchema->GetClasses();<br>.....<br> classDef = FdoCommonSchemaUtil::DeepCopyFdoClassDefinition(classDef, NULL);<br> FDO_SAFE_ADDREF(classDef.p);<br> classes->Add(classDef);<br>
}<br><br><br>I find this all a bit difficult to sort out, but could it be all the addref's, and the possibility that the classes collection<br>
doesn't free resources properly ?<br>
<br>I have also looked through the our code (using .NET wrapper) , and there is using() statments on all references.<br><br>Note that I get about 140 leaks in this example, using only 1 layer/dataset. <br><br><br>-- Oyvind<br>
<br><br><br><br><br><br><br><br><br><div class="gmail_quote">On Tue, Feb 22, 2011 at 5:07 PM, Oyvind Idland <span dir="ltr"><<a href="mailto:oyvind.idland@gmail.com">oyvind.idland@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I tracked just one leak, and it appears to come from the FDO framework itself.<br><br>I'm not in my office right now, but I also saw a SAFE_ADDREF macro or something <br>like that being used on the same pointer during the callstack, could it be ref's that doesn't <br>
get released ? (didn't study in detail)<br><br><br>-- Oyvind<br><br><br><br><div class="gmail_quote"><div><div></div><div class="h5">On Tue, Feb 22, 2011 at 4:39 PM, Greg Boone <span dir="ltr"><<a href="mailto:greg.boone@autodesk.com" target="_blank">greg.boone@autodesk.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">The FDO API is fairly good when it comes to controlling memory. The ArcSDE provider itself may not be as efficient. If you have any details, please send them
and/or create a trac ticket.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Greg</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:fdo-users-bounces@lists.osgeo.org" target="_blank">fdo-users-bounces@lists.osgeo.org</a> [mailto:<a href="mailto:fdo-users-bounces@lists.osgeo.org" target="_blank">fdo-users-bounces@lists.osgeo.org</a>]
<b>On Behalf Of </b>Oyvind Idland<br>
<b>Sent:</b> Tuesday, February 22, 2011 10:18 AM<br>
<b>To:</b> FDO Users Mail List<br>
<b>Subject:</b> [fdo-users] Memory leaks - lots of them ?</span></p><div><div></div><div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I get lots of memory leaks when debugging the trunk code. <br>
<br>
Is there being done any checks for leaks by the coders ?<br>
<br>
Let me know if you need some more info.<br>
<br>
<br>
<br>
-- Oyvind</p>
</div></div></div>
</div>
<br></div></div>_______________________________________________<br>
fdo-users mailing list<br>
<a href="mailto:fdo-users@lists.osgeo.org" target="_blank">fdo-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-users</a><br>
<br></blockquote></div><br>
</blockquote></div><br>