topic Re: Insert feature causes Out of memory exception in ArcObjects SDK Questions

Insert feature causes Out of memory exception

AlexeySubbotin — Wed, 13 Mar 2013 14:42:47 GMT

Hi!
I'm developing the 3D modeling GIS software. For 3D city models i use generated from vector data building models and 3d files (Google Earth and SketchUp) with geographic coordinates within. I import such files' geometries with IImport3DFile and store them in multipatch featureclass in file geodatabase.
At last I recieved an exception "Out of memory" during IFeatureCursor.InsertFeature. Have to say that there was no such a problem before (with other files). Error appears constantly after processing definite number of files. Geometries i load from them are correct, i processing their footprints and if i don't save them to my featureclass i process them all with no exceptions. After the exception appears program can't work properly at all until restart (looks like ArcObjects crash).
How you could understand i use insert cursor with featurebuffer. Tried edit sessions, load mode for featureclass, direct write with WriteFeature and so on... No differences. May anybody help me? Any suggestions?
Sorry for my English )

Re: Insert feature causes Out of memory exception

JasonPike — Wed, 13 Mar 2013 15:02:20 GMT

Hi!
I'm developing the 3D modeling GIS software. For 3D city models i use generated from vector data building models and 3d files (Google Earth and SketchUp) with geographic coordinates within. I import such files' geometries with IImport3DFile and store them in multipatch featureclass in file geodatabase.
At last I recieved an exception "Out of memory" during IFeatureCursor.InsertFeature. Have to say that there was no such a problem before (with other files). Error appears constantly after processing definite number of files. Geometries i load from them are correct, i processing their footprints and if i don't save them to my featureclass i process them all with no exceptions. After the exception appears program can't work properly at all until restart (looks like ArcObjects crash).
How you could understand i use insert cursor with featurebuffer. Tried edit sessions, load mode for featureclass, direct write with WriteFeature and so on... No differences. May anybody help me? Any suggestions?
Sorry for my English )

Can you post code samples for where you are loading models?

What language are you using for development?

If you are using a .NET language, you can try using CLRProfiler to identify what is consuming the most memory. If it isn't a managed memory issue, you can use UMDH to see what is being allocated on the unmanaged heap.

Let me know if I can help.

Re: Insert feature causes Out of memory exception

AlexeySubbotin — Thu, 14 Mar 2013 09:10:23 GMT

Can you post code samples for where you are loading models?

What language are you using for development?

If you are using a .NET language, you can try using CLRProfiler to identify what is consuming the most memory. If it isn't a managed memory issue, you can use UMDH to see what is being allocated on the unmanaged heap.

Let me know if I can help.

Hi, ScJpike!
I use C# with .NET Framework 4.0

There is code fragments of my project for you to test:
Loading each model is made with following class instance (one class instance represents one file):

//class implementation code fragment
public enum GeoReferencedModelAltitudeType { relativeToGround, absolute, clampToGround }

public class GeoReferencedModel
{

public string Filename { get; set; }

//properties are set while reading file
public double Longitude { get; private set; }
public double Latitude { get; private set; }
public double Altitude { get; private set; }
public GeoReferencedModelAltitudeType AltitudeType { get; private set; }
public double XAngle { get; private set; }
public double YAngle { get; private set; }
public double ZAngle { get; private set; }
public double ScaleX { get; private set; }
public double ScaleY { get; private set; }
public double ScaleZ { get; private set; }

public GeoReferencedModel(string filename)
{
Filename = filename;
ScaleX = ScaleY = ScaleZ = 1;
}

public IPoint get_Placement()
{
//read file and assign class properties
//no ArcObjects use

//just for test with a model
Longitude = 51.310704;
Latitude = 35.731657;
Altitude = 0;
AltitudeType = GeoReferencedModelAltitudeType.relativeToGround;
ZAngle = 0;
XAngle = 0;
YAngle = 0;
ScaleX = 1;
ScaleY = 1;
ScaleZ = 1;

IPoint point = new PointClass();
point.PutCoords(Longitude, Latitude);
        return point;
}

private void set_ModelAltitude(IPoint placement)
{
switch (AltitudeType)
{
case GeoReferencedModelAltitudeType.absolute:
   placement.Z = Altitude;
   break;
case GeoReferencedModelAltitudeType.clampToGround:
   break;
case GeoReferencedModelAltitudeType.relativeToGround:
   placement.Z = placement.Z + Altitude;
   break;
}
}

public IGeometry get_MultiPatch(IPoint placement, ISpatialReference spatialReference)
{
IGeometry geometry = null;
IImport3DFile import3DFile = new Import3DFileClass();
try
{
import3DFile.CreateFromFile(Filename);
geometry = import3DFile.Geometry;
((IImport3DFileRoots)import3DFile).ReleaseCurrentFile();
}
catch
{
geometry = null;
}
finally
{
System.Runtime.InteropServices.Marshal.ReleaseComObject(import3DFile);
}

if (geometry != null)
{
set_ModelAltitude(placement);
IVector3D xVector = constructVector3D(10, 0, 0);
IVector3D yVector = constructVector3D(0, 10, 0);
IVector3D zVector = constructVector3D(0, 0, 10);
((ITransform3D)geometry).RotateVector3D(xVector, XAngle * (Math.PI / 180));
((ITransform3D)geometry).RotateVector3D(yVector, YAngle * (Math.PI / 180));
((ITransform3D)geometry).RotateVector3D(zVector, ZAngle * (Math.PI / 180));
((ITransform3D)geometry).Move3D(placement.X, placement.Y, placement.Z);
((ITransform3D)geometry).Scale3D(placement, ScaleX, ScaleY, ScaleZ);
geometry.SpatialReference = spatialReference;
geometry.SnapToSpatialReference();
}

return geometry;
}

}

Processing all model files with inserting them into file geodatabase featureclass is made by following method:

public static class Tools
{

public static void Import3DFiles(string GDBFilename, string Dataset, List<GeoReferencedModel> Files, ISpatialReference DatasetSpatialReference)
{
IWorkspaceFactory wsf = new FileGDBWorkspaceFactoryClass();
IWorkspace datasetWorkspace=wsf.OpenFromFile(GDBFilename, 0);
System.Runtime.InteropServices.Marshal.ReleaseComObject(wsf);

IFeatureClass objectiveFeatureClass;
exist = ((IWorkspace2)datasetWorkspace).get_NameExists(esriDatasetType.esriDTFeatureClass, Dataset);
if (!exist)
{

             IFieldEdit fieldEdit;

IField shapeField = new FieldClass();
fieldEdit = (IFieldEdit) shapeField;
fieldEdit.Name_2 = "Shape";
             fieldEdit.Type_2 = esriFieldType.esriFieldTypeGeometry;

IGeometryDef geometryDef = new GeometryDefClass();
             IGeometryDefEdit geometryDefEdit;
             geometryDefEdit = (IGeometryDefEdit)geometryDef;
             geometryDefEdit.GeometryType_2 = esriGeometryType.esriGeometryMultiPatch;
             geometryDefEdit.GridCount_2 = 1;
             geometryDefEdit.set_GridSize(0, 0);
             geometryDefEdit.HasZ_2 = true;
             geometryDefEdit.HasM_2 = false;
             if (DatasetSpatialReference != null) geometryDefEdit.SpatialReference_2 = DatasetSpatialReference; else geometryDefEdit.SpatialReference_2 = new UnknownCoordinateSystemClass();
             fieldEdit.GeometryDef_2 = geometryDef;

IField oidField = new FieldClass();
fieldEdit = (IFieldEdit) oidField;
fieldEdit.Name_2 = "OID";
             fieldEdit.Type_2 = esriFieldType.esriFieldTypeOID;
fieldEdit.Precision_2 = 0;

IFields fcFields = new FieldsClass();
IFieldsEdit fcFieldsEdit = (IFieldsEdit)fcFields;
fcFieldsEdit.AddField(shapeField);
fcFieldsEdit.AddField(oidField);

IFieldChecker fieldChecker = new FieldCheckerClass();
IEnumFieldError enumFieldError = null;
IFields validatedFields = null;
fieldChecker.ValidateWorkspace = datasetWorkspace;
fieldChecker.Validate(fields, out enumFieldError, out validatedFields);

IObjectClassDescription objectDescription = new FeatureClassDescriptionClass();
objectiveFeatureClass = ((IFeatureWorkspace)datasetWorkspace).CreateFeatureClass(dataset, validatedFields, null, objectDescription.ClassExtensionCLSID, esriFeatureType.esriFTSimple, shapeField.Name, "");
}
else
objectiveFeatureClass = ((IFeatureWorkspace)datasetWorkspace).OpenFeatureClass(dataset);

((ISchemaLock)objectiveFeatureClass).ChangeSchemaLock(esriSchemaLock.esriExclusiveSchemaLock);
((IFeatureClassLoad)objectiveFeatureClass).LoadOnlyMode = true;

ISpatialReferenceFactory srFactory = new SpatialReferenceEnvironmentClass();
IGeographicCoordinateSystem gcs = srFactory.CreateGeographicCoordinateSystem(gcsType);
ISpatialReference geoSR = (ISpatialReference)gcs;
ISpatialReferenceResolution srResolution = (ISpatialReferenceResolution)sr;
        srResolution.ConstructFromHorizon();
        srResolution.SetDefaultMResolution();
        srResolution.SetDefaultXYResolution();
        srResolution.SetDefaultZResolution();
        ISpatialReferenceTolerance srTolerance = (ISpatialReferenceTolerance)sr;
        srTolerance.SetDefaultMTolerance();
        srTolerance.SetDefaultXYTolerance();
        srTolerance.SetDefaultZTolerance();
set_ResolutionTolerance(sr);
System.Runtime.InteropServices.Marshal.ReleaseComObject(srFactory);

featureBuffer = objectiveFeatureClass.CreateFeatureBuffer();
featureCursor = objectiveFeatureClass.Insert(true);

foreach (string geoReferencedModel in Files)
{
//reading lat,long and other values values from files with own SketchUpReader (for *.skp) and ZipForge, XDocument (for *.kmz)
//do not use any ArcObjects
IPoint placement = geoReferencedModel.get_Placement();
placement.SpatialReference = geoSR;
(IZAware)geometry.ZAware = true;
placement.Project(DatasetSpatialReference);

//get Z value from IFunctionalSurface (relief raster)
//just for test
placement.Z = 0;

if (!placement.Z.Equals(double.NaN))
{
                 IGeometry multiPatch=null;
   //import file's geometry
                        multiPatch = geoReferencedModel.get_MultiPatch(placement, DatasetSpatialReference);
   if (multiPatch != null)
   {
    featureBuffer.Shape = multiPatch;
                                featureCursor.InsertFeature(featureBuffer);

    /*tried to flush cursor and create new instances cursor and buffer
    featureCursor.Flush();
    featureBuffer = objectiveFeatureClass.CreateFeatureBuffer();
    featureCursor = objectiveFeatureClass.Insert(true);
    */

    /*tried to use cursor with no buffering here and in declaration
    featureCursor.Flush();
    featureBuffer = objectiveFeatureClass.CreateFeatureBuffer();
    featureCursor = objectiveFeatureClass.Insert(false);
    */

    /*tried such variant with no featurebuffer and featurecursor at all
    IFeature newFeature = objectiveFeatureClass.CreateFeature();
    newFeature.Shape = multipatch;
    ((IFeatureClassWrite)objectiveFeatureClass).WriteFeature(newFeature);
    */

    //here i compute a footprint of multipatch and store it in another featureclass

                                System.Runtime.InteropServices.Marshal.ReleaseComObject(placement);
                                System.Runtime.InteropServices.Marshal.ReleaseComObject(multiPatch);
                                System.Runtime.InteropServices.Marshal.CleanupUnusedObjectsInCurrentContext();
                                GC.Collect();
   }
}

}

featureCursor.Flush();
System.Runtime.InteropServices.Marshal.ReleaseComObject(featureCursor);

((IFeatureClassLoad)objectiveFeatureClass).LoadOnlyMode = false;
((ISchemaLock)objectiveFeatureClass).ChangeSchemaLock(esriSchemaLock.esriSharedSchemaLock);

}

}

Re: Insert feature causes Out of memory exception

AlexeySubbotin — Thu, 14 Mar 2013 09:12:47 GMT

To test my code from previous post i prepared a code fragment

//for test
//may need some correction as was configured and modified on-the-fly from project

ISpatialReferenceFactory3 srFactory = new SpatialReferenceEnvironmentClass();
IProjectedCoordinateSystem pcs = srFactory.CreateProjectedCoordinateSystem(pcsType);

ISpatialReference spatialReference = (ISpatialReference)pcs;
ISpatialReferenceResolution srResolution = (ISpatialReferenceResolution)spatialReference;
srResolution.ConstructFromHorizon();
srResolution.SetDefaultMResolution();
srResolution.SetDefaultXYResolution();
srResolution.SetDefaultZResolution();
ISpatialReferenceTolerance srTolerance = (ISpatialReferenceTolerance)spatialReference;
srTolerance.SetDefaultMTolerance();
srTolerance.SetDefaultXYTolerance();
srTolerance.SetDefaultZTolerance();

IVerticalDatum verticalDatum = srFactory.CreateVerticalDatum((int)esriSRVerticalDatumType.esriSRVertDatum_SeaLevel);
IHVDatum hvDatum = verticalDatum as IHVDatum;
ILinearUnit unit = srFactory.CreateUnit((int)esriSRUnitType.esriSRUnit_Meter) as ILinearUnit;
IVerticalCoordinateSystemEdit vcsEdit = (IVerticalCoordinateSystemEdit)new VerticalCoordinateSystemClass();
int positive = 1;
double shift = 0;
vcsEdit.DefineEx("", "", "", "", "", hvDatum, unit, ref shift, ref positive);
((ISpatialReference3)spatialReference).VerticalCoordinateSystem = (IVerticalCoordinateSystem)vcsEdit;
ISpatialReferenceResolution sprefResolution = (ISpatialReferenceResolution)spatialReference;
sprefResolution.SetDefaultZResolution();
ISpatialReferenceTolerance srTolerance = (ISpatialReferenceTolerance)spatialReference;
srTolerance.SetDefaultZTolerance();
spatialReference.Changed();

System.Runtime.InteropServices.Marshal.ReleaseComObject(srFactory);

List<GeoReferencedModel> models=new List<GeoReferencedModel>();
models.Add(new GeoReferencedModel(path_to_model));

IWorkspaceFactory2 workspaceFactory = new FileGDBWorkspaceFactoryClass();
IWorkspaceName workspaceName = workspaceFactory.Create(System.IO.Path.GetDirectoryName(path_to_fileGDB), System.IO.Path.GetFileName(path_to_fileGDB), null, 0);
IName name = (IName)workspaceName;
IWorkspace workspace = (IWorkspace)name.Open();
System.Runtime.InteropServices.Marshal.ReleaseComObject(workspaceFactory);
System.Runtime.InteropServices.Marshal.ReleaseComObject(workspaceName);

Import3DFiles(path_to_fileGDB, "GeoReferencedObjects3D", models, spatialReference)

I see that the model causing error is large enough (kmz file 13Mb), and may be featureclass can't store such amount of information by igeometry field. If so is, so how i can analyze geometries of 3d files to prevent exceptions with attempts to store them? What is maximum size of such objects?
Can't to attach model file because of size restrictions. If you would like i can email it to you.
Would be very appreciative for your help.

Re: Insert feature causes Out of memory exception

JasonPike — Fri, 15 Mar 2013 15:37:17 GMT

To test my code from previous post i prepared a code fragment

//for test
//may need some correction as was configured and modified on-the-fly from project

ISpatialReferenceFactory3 srFactory = new SpatialReferenceEnvironmentClass();
IProjectedCoordinateSystem pcs = srFactory.CreateProjectedCoordinateSystem(pcsType);

ISpatialReference spatialReference = (ISpatialReference)pcs;
ISpatialReferenceResolution srResolution = (ISpatialReferenceResolution)spatialReference;
srResolution.ConstructFromHorizon();
srResolution.SetDefaultMResolution();
srResolution.SetDefaultXYResolution();
srResolution.SetDefaultZResolution();
ISpatialReferenceTolerance srTolerance = (ISpatialReferenceTolerance)spatialReference;
srTolerance.SetDefaultMTolerance();
srTolerance.SetDefaultXYTolerance();
srTolerance.SetDefaultZTolerance();

IVerticalDatum verticalDatum = srFactory.CreateVerticalDatum((int)esriSRVerticalDatumType.esriSRVertDatum_SeaLevel);
IHVDatum hvDatum = verticalDatum as IHVDatum;
ILinearUnit unit = srFactory.CreateUnit((int)esriSRUnitType.esriSRUnit_Meter) as ILinearUnit;
IVerticalCoordinateSystemEdit vcsEdit = (IVerticalCoordinateSystemEdit)new VerticalCoordinateSystemClass();
int positive = 1;
double shift = 0;
vcsEdit.DefineEx("", "", "", "", "", hvDatum, unit, ref shift, ref positive);
((ISpatialReference3)spatialReference).VerticalCoordinateSystem = (IVerticalCoordinateSystem)vcsEdit;
ISpatialReferenceResolution sprefResolution = (ISpatialReferenceResolution)spatialReference;
sprefResolution.SetDefaultZResolution();
ISpatialReferenceTolerance srTolerance = (ISpatialReferenceTolerance)spatialReference;
srTolerance.SetDefaultZTolerance();
spatialReference.Changed();

System.Runtime.InteropServices.Marshal.ReleaseComObject(srFactory);

List<GeoReferencedModel> models=new List<GeoReferencedModel>();
models.Add(new GeoReferencedModel(path_to_model));

IWorkspaceFactory2 workspaceFactory = new FileGDBWorkspaceFactoryClass();
IWorkspaceName workspaceName = workspaceFactory.Create(System.IO.Path.GetDirectoryName(path_to_fileGDB), System.IO.Path.GetFileName(path_to_fileGDB), null, 0);
IName name = (IName)workspaceName;
IWorkspace workspace = (IWorkspace)name.Open();
System.Runtime.InteropServices.Marshal.ReleaseComObject(workspaceFactory);
System.Runtime.InteropServices.Marshal.ReleaseComObject(workspaceName);

Import3DFiles(path_to_fileGDB, "GeoReferencedObjects3D", models, spatialReference)

I see that the model causing error is large enough (kmz file 13Mb), and may be featureclass can't store such amount of information by igeometry field. If so is, so how i can analyze geometries of 3d files to prevent exceptions with attempts to store them? What is maximum size of such objects?
Can't to attach model file because of size restrictions. If you would like i can email it to you.
Would be very appreciative for your help.

Have you tried only loading the model that has the problem? Or, does the problem only occur if you load a bunch of models and then the model that is having trouble?

Re: Insert feature causes Out of memory exception

AlexeySubbotin — Fri, 15 Mar 2013 16:55:52 GMT

Have you tried only loading the model that has the problem? Or, does the problem only occur if you load a bunch of models and then the model that is having trouble?

The problem occur with single model too. No differences bunch of models or single model.

Re: Insert feature causes Out of memory exception

JasonPike — Fri, 15 Mar 2013 17:16:20 GMT

The problem occur with single model too. No differences bunch of models or single model.

Ok. Can you create and send a project that loads that particular model and reproduces the failure? Please include the model in the zip. I'll try to find out what is consuming the memory.

I'd also report this as a bug to ESRI.

Re: Insert feature causes Out of memory exception

AlexeySubbotin — Fri, 15 Mar 2013 19:01:48 GMT

Ok. Can you create and send a project that loads that particular model and reproduces the failure? Please include the model in the zip. I'll try to find out what is consuming the memory.

I'd also report this as a bug to ESRI.

Of course. I don't have such an ability at home (weekend you know). Once i'll get to office, i'll make it. Such a question. How can i send it, if it's size exceeds the limits for attachments? Only model is 12.8 MB, while limit for zip is 2.00 MB.

Re: Insert feature causes Out of memory exception

JasonPike — Mon, 18 Mar 2013 13:24:37 GMT

Of course. I don't have such an ability at home (weekend you know). Once i'll get to office, i'll make it. Such a question. How can i send it, if it's size exceeds the limits for attachments? Only model is 12.8 MB, while limit for zip is 2.00 MB.

Could you post it on Dropbox or some equivalent and post a link?

Re: Insert feature causes Out of memory exception

AlexeySubbotin — Mon, 18 Mar 2013 13:50:32 GMT

Could you post it on Dropbox or some equivalent and post a link?

Hi, Jason. I created the project.
Despite the common logic of the test project and the source, the test project produces another exception, but it occurs at the same operator (insert a feature to the feature class).
Depending on the type of call (in the current thread or in new one) it can be the RCP_E_SERVERFAULT exception wit error code -2147417851 or the external object's exception with error code -2147467259. Also the project is based on .NET Framework 3.5 (as it should be for ArcObjects 10). Couldn't to base it on .NET Framework 4.0, and honestly don't realy understand how it happened with my source project. Maybe the difference of exceptions raised by the projects explaned by different framework they are based on. After all the exception remains and it raises constantly.

Link to archive http://dl.dropbox.com/u/91176632/Test.zip

Re: Insert feature causes Out of memory exception

JasonPike — Mon, 18 Mar 2013 16:11:53 GMT

Hi, Jason. I created the project.
Despite the common logic of the test project and the source, the test project produces another exception, but it occurs at the same operator (insert a feature to the feature class).
Depending on the type of call (in the current thread or in new one) it can be the RCP_E_SERVERFAULT exception wit error code -2147417851 or the external object's exception with error code -2147467259. Also the project is based on .NET Framework 3.5 (as it should be for ArcObjects 10). Couldn't to base it on .NET Framework 4.0, and honestly don't realy understand how it happened with my source project. Maybe the difference of exceptions raised by the projects explaned by different framework they are based on. After all the exception remains and it raises constantly.

Link to archive http://dl.dropbox.com/u/91176632/Test.zip

Ok. I have downloaded your project and the ZipForge dependency.

Here are some of my findings:

1) The reason you were getting the COM Exception was most likely because the projects targeted "Any CPU" instead of "x86". I changed it to "x86" and the exception went away.

2) The reason you could not compile against .NET 4.0 is because the "Embed Interop Types" property was set to true on the ESRI assembly references. If you change "Embed Interop Types" to false for all the ESRI references in the project, it will build against .NET 4.0.

After I got all that sorted out, I stepped through the solution and it succeeded. I succeeded against .NET 3.5 and .NET 4.0. I did notice some places we could improve the COM interop in the code, but we'll look at that later.

Please try the changes I suggest above and see if the test project succeeds for you.

Re: Insert feature causes Out of memory exception

AlexeySubbotin — Tue, 19 Mar 2013 10:06:20 GMT

Ok. I have downloaded your project and the ZipForge dependency.

Here are some of my findings:

1) The reason you were getting the COM Exception was most likely because the projects targeted "Any CPU" instead of "x86". I changed it to "x86" and the exception went away.

2) The reason you could not compile against .NET 4.0 is because the "Embed Interop Types" property was set to true on the ESRI assembly references. If you change "Embed Interop Types" to false for all the ESRI references in the project, it will build against .NET 4.0.

After I got all that sorted out, I stepped through the solution and it succeeded. I succeeded against .NET 3.5 and .NET 4.0. I did notice some places we could improve the COM interop in the code, but we'll look at that later.

Please try the changes I suggest above and see if the test project succeeds for you.

Ok, i have tried your suggestions.
Target platform was set to "x86" just when my primary source solution was started. I think, it was lost when i "extracted" the test project from it.
At last i even made the configuration for x86 platform in the solution properties. It doesn't help.
Compiled the test project against .NET 3.5 and 4.0. The result is one-exception.
Tried to build and execute the project on another PC with the same result.
At first run application, maybe, didn't checkout 3DAnalyst license and completed with no errors. Of course it didn't import the test model, even didn't open it (IImport3DFile.CreateFromFile failed). I revealed it while debugging with step into along the code. I revealed also that the application was initialized with an Engine Product Code.
So i made some changes to initialize it with an ArcView Product Code (as 3DAnalyst not authorized with Engine). It prevented the application from the "import 3d model" exception but as expected the "insert feature" exception was thrown.
Also while testing my primary and test projects i noticed that almost any model with it's size more than 5 MB (i mean kmz models, skp was not tested for "the size restrictions" yet) can't be processed correctly.

Re: Insert feature causes Out of memory exception

JasonPike — Sun, 12 Dec 2021 06:52:50 GMT

Ok, i have tried your suggestions.
Target platform was set to "x86" just when my primary source solution was started. I think, it was lost when i "extracted" the test project from it.
At last i even made the configuration for x86 platform in the solution properties. It doesn't help.
Compiled the test project against .NET 3.5 and 4.0. The result is one-exception.
Tried to build and execute the project on another PC with the same result.
At first run application, maybe, didn't checkout 3DAnalyst license and completed with no errors. Of course it didn't import the test model, even didn't open it (IImport3DFile.CreateFromFile failed). I revealed it while debugging with step into along the code. I revealed also that the application was initialized with an Engine Product Code.
So i made some changes to initialize it with an ArcView Product Code (as 3DAnalyst not authorized with Engine). It prevented the application from the "import 3d model" exception but as expected the "insert feature" exception was thrown.
Also while testing my primary and test projects i noticed that almost any model with it's size more than 5 MB (i mean kmz models, skp was not tested for "the size restrictions" yet) can't be processed correctly.

I see. The suggestions I made were to get the test project running on your machine. I think that is an important first step.

I should mention that I'm using ArcGIS 10.1 for Desktop on a Windows 7 64-bit machine with 8GB of RAM. Please provide this information for your machine. I had made the following changes to the license checkout code:

if (licenseInit.InitializeApplication(new esriLicenseProductCode[] { esriLicenseProductCode.esriLicenseProductCodeStandard,
new esriLicenseExtensionCode[] { esriLicenseExtensionCode.esriLicenseExtensionCode3DAnalyst }))

Also, I stepped through the code and made sure that no exceptions were occurring and that the field was populated when I reached the InsertFeature call.

If you get exceptions or build errors, please post them--they will help me determine what is going on on your machine.

What build error do you get when you target 4.0?

What are the details of the exception you are getting?

Thanks!
Jason

Re: Insert feature causes Out of memory exception

JasonPike — Sun, 12 Dec 2021 06:52:59 GMT

Well, I did find some memory leaks. Looks like ESRI uses the open source project Little CMS and either doesn't release something returned from one of its calls, or Little CMS has a memory leak. While 3MB of leaked memory isn't small, I doubt it is your problem. I still can't reproduce the error on my machine, possibly because it doesn't happen in 10.1. So, what we can try next is using UMDH to see what is in memory when your program crashes. I'll post instructions in a different post. Also, it is possible that there is plenty of memory available, but due to improper pinning of GCHandles, the .NET allocator is unable to compact the GCHeap and therefore runs out of available memory. We'd need to use WinDbg, SOS, and SOSEX to find that, so will start with the easy stuff first.
+ 2896592 ( 2896592 -      0)     83 allocs BackTrace87C2B4C
+      83 (     83 -      0) BackTrace87C2B4C allocations

 ntdll!RtlAllocateHeap+00000274
 LCMS117LIB!cmsCreateMultiprofileTransform+000005A3

It is also possible that this transform is created once and kept around for the lifetime of the process--it may not be a leak. I think it still warrants asking about.

Re: Insert feature causes Out of memory exception

JasonPike — Sun, 12 Dec 2021 06:53:02 GMT

INSTALLING THE NECESSARY TOOLS:

1. Download Debugging Tools for Windows. You will likely have to download the entire Windows SDK, but you can browse the ISO for the dbg_x86.msi and just install it. Make sure and install the x86 version regardless of your machine's architecture.
http://msdn.microsoft.com/en-us/wind.../gg463009.aspx

2. Add a User Environment Variable called _NT_SYMBOL_PATH and set its value to this:

cache*C:\dev\symbols;SRV*C:\dev\symbols*http://msdl.microsoft.com/download/symbols;SRV*C:\dev\symbols*http://downloads2.esri.com/Support/symbols/

This will allow you to resolve the debugging symbols you need.

3. Add a System Environment variable called OANOCACHE and set its value to 1. The disables Ole Automation caching, which is necessary to get accurate information about which calls allocated memory.

4. [OPTIONAL] Add the Debugging Tools for Windows path to you User Environment Variables (C:\Program Files (x86)\Debugging Tools for Windows (x86)\ for x64 machines, C:\Program Files\Debugging Tools for Windows (x86)\ for x86 machines)

USING UMDH TO ANALYZE PROBLEM:

5. Use gflags to turn stack tracing on:
gflags -i <name of executable, e.g. Test.exe> +ust
If you are running a standalone application that uses ArcObjects, replace arcmap.exe with the name of your executable.

6. Start your application.

7. Mark memory before executing the code you suspect is leaking memory by running UMDH:
umdh -pn:arcmap.exe -f:mark1.txt

NOTE: In some cases, the process runs start to finish with no stops for user input. In this case, you might want to add Console.ReadKey() (and a message to let you know it is waiting) around the area you suspect is leaking memory so you can take snapshots.

8. Execute the code that you suspect is leaking memory and the code that you think should release memory.

9. Mark memory again after step 8 is complete:
umdh -pn:arcmap.exe -f:mark2.txt

NOTE: Try taking a snapshot at the point the out-of-memory exception occurs.

10. Create a diff file for the two marks:
umdh -d mark1.txt mark2.txt -f:results.txt

TIP: The -d switch just outputs in decimal format rather than hexadecimal and makes it easier to read.

11. Open the text file to find something like the following:

<Lots of information about the symbol files that were loaded?
...
<Stacks for allocated memory in order from highest consumption to lowest consumption>

+ 1520000 ( 1520000 - 0) 10000 allocs BackTrace106BF720
+ 10000 ( 10000 - 0) BackTrace106BF720 allocations

ntdll!RtlAllocateHeap+00000274
MSVCR90!malloc+00000079
MSVCR90!operator new+0000001F
Geometry!ESRI::Point::Clone+0000000D
EngineGraphics!GraphicTracker::AddWithOptions+0000004D
EngineGraphics!GraphicTracker::Add+00000051
mscorwks!CLRToCOMWorker+0000019A
<no module>!???+00000000 : 3CA70A

+ 1520000 ( 1520000 - 0) 10000 allocs BackTraceB522378
+ 10000 ( 10000 - 0) BackTraceB522378 allocations

ntdll!RtlAllocateHeap+00000274
MSVCR90!malloc+00000079
MSVCR90!operator new+0000001F
Geometry!ESRI::Point::Clone+0000000D
EngineGraphics!GraphicTracker::GetGT+00000087
EngineGraphics!GraphicTracker::AddReplaceGeometryToDraw+00000102
EngineGraphics!GraphicTracker::AddWithOptions+0000019A
EngineGraphics!GraphicTracker::Add+00000051
mscorwks!CLRToCOMWorker+0000019A
<no module>!???+00000000 : 3CA70A

CLEANUP AFTER YOU'RE DONE ANALYZING:

Do the following to make sure you machine performance is optimal when you aren't debugging:

12. Use the following to turn off stack tracing when you are finished.
gflags -i arcmap.exe -ust

13. Set OANOCACHE to 0.

Re: Insert feature causes Out of memory exception

AlexeySubbotin — Sun, 12 Dec 2021 06:53:04 GMT

INSTALLING THE NECESSARY TOOLS:

1. Download Debugging Tools for Windows. You will likely have to download the entire Windows SDK, but you can browse the ISO for the dbg_x86.msi and just install it. Make sure and install the x86 version regardless of your machine's architecture.
http://msdn.microsoft.com/en-us/wind.../gg463009.aspx

2. Add a User Environment Variable called _NT_SYMBOL_PATH and set its value to this:
cache*C:\dev\symbols;SRV*C:\dev\symbols*http://msdl.microsoft.com/download/symbols;SRV*C:\dev\symbols*http://downloads2.esri.com/Support/symbols/
This will allow you to resolve the debugging symbols you need.

3. Add a System Environment variable called OANOCACHE and set its value to 1. The disables Ole Automation caching, which is necessary to get accurate information about which calls allocated memory.

4. [OPTIONAL] Add the Debugging Tools for Windows path to you User Environment Variables (C:\Program Files (x86)\Debugging Tools for Windows (x86)\ for x64 machines, C:\Program Files\Debugging Tools for Windows (x86)\ for x86 machines)

USING UMDH TO ANALYZE PROBLEM:

5. Use gflags to turn stack tracing on:
gflags -i <name of executable, e.g. Test.exe> +ust
If you are running a standalone application that uses ArcObjects, replace arcmap.exe with the name of your executable.

6. Start your application.

7. Mark memory before executing the code you suspect is leaking memory by running UMDH:
umdh -pn:arcmap.exe -f:mark1.txt

NOTE: In some cases, the process runs start to finish with no stops for user input. In this case, you might want to add Console.ReadKey() (and a message to let you know it is waiting) around the area you suspect is leaking memory so you can take snapshots.

8. Execute the code that you suspect is leaking memory and the code that you think should release memory.

9. Mark memory again after step 8 is complete:
umdh -pn:arcmap.exe -f:mark2.txt

NOTE: Try taking a snapshot at the point the out-of-memory exception occurs.

10. Create a diff file for the two marks:
umdh -d mark1.txt mark2.txt -f:results.txt

TIP: The -d switch just outputs in decimal format rather than hexadecimal and makes it easier to read.

11. Open the text file to find something like the following:

<Lots of information about the symbol files that were loaded?
...
<Stacks for allocated memory in order from highest consumption to lowest consumption>
+ 1520000 ( 1520000 - 0) 10000 allocs BackTrace106BF720
+ 10000 ( 10000 - 0) BackTrace106BF720 allocations

ntdll!RtlAllocateHeap+00000274
MSVCR90!malloc+00000079
MSVCR90!operator new+0000001F
Geometry!ESRI::Point::Clone+0000000D
EngineGraphics!GraphicTracker::AddWithOptions+0000004D
EngineGraphics!GraphicTracker::Add+00000051
mscorwks!CLRToCOMWorker+0000019A
<no module>!???+00000000 : 3CA70A

+ 1520000 ( 1520000 - 0) 10000 allocs BackTraceB522378
+ 10000 ( 10000 - 0) BackTraceB522378 allocations

ntdll!RtlAllocateHeap+00000274
MSVCR90!malloc+00000079
MSVCR90!operator new+0000001F
Geometry!ESRI::Point::Clone+0000000D
EngineGraphics!GraphicTracker::GetGT+00000087
EngineGraphics!GraphicTracker::AddReplaceGeometryToDraw+00000102
EngineGraphics!GraphicTracker::AddWithOptions+0000019A
EngineGraphics!GraphicTracker::Add+00000051
mscorwks!CLRToCOMWorker+0000019A
<no module>!???+00000000 : 3CA70A
CLEANUP AFTER YOU'RE DONE ANALYZING:

Do the following to make sure you machine performance is optimal when you aren't debugging:

12. Use the following to turn off stack tracing when you are finished.
gflags -i arcmap.exe -ust

13. Set OANOCACHE to 0.

So, i have followed your instructions and received the results. I'm not good in such debugging, so can't to evaluate it enough.
I think you mean something about this when was talking about leaks (just one example):

+ 249397232 ( 249397232 -      0)      1 allocs BackTraceF3D0738
+       1 (      1 -      0) BackTraceF3D0738 allocations

 ntdll!RtlUlonglongByteSwap+00000B52
 MSVCR90!malloc+00000079
 FileGDB!DllRegisterServer+000053E8
 FileGDB!DllCanUnloadNow+0001C5DA
 FileGDB!???+00000000 : 69BC62F5
 FileGDB!???+00000000 : 69BC694A
 RPCRT4!NdrServerInitialize+00000240
 RPCRT4!NdrStubCall2+00000256
 ole32!WdtpInterfacePointer_UserUnmarshal+0000256F
 OLEAUT32!CreateErrorInfo+00000268
 ole32!WdtpInterfacePointer_UserUnmarshal+000025FF
 ole32!WdtpInterfacePointer_UserUnmarshal+00002B59
 ole32!CoTaskMemFree+00001B02
 ole32!CoTaskMemFree+000019F7
 ole32!DcomChannelSetHResult+000008FF
 ole32!WdtpInterfacePointer_UserUnmarshal+00002A56
 ole32!WdtpInterfacePointer_UserUnmarshal+000028CA
 ole32!WdtpInterfacePointer_UserUnmarshal+00002F86
 ole32!DcomChannelSetHResult+0000075C
 ole32!DcomChannelSetHResult+0000071B
 USER32!gapfnScSendMessage+00000332
 USER32!GetThreadDesktop+000000D7
 USER32!CharPrevW+00000138
 USER32!DispatchMessageW+0000000F
 ole32!CoWaitForMultipleHandles+00004311
 ole32!CoWaitForMultipleHandles+000023C1
 ole32!CoWaitForMultipleHandles+00004332
 ole32!CoGetTreatAsClass+00002619
 ole32!CoGetTreatAsClass+0000314B
 KERNEL32!BaseThreadInitThunk+00000012
 ntdll!RtlInitializeExceptionChain+00000063
 ntdll!RtlInitializeExceptionChain+00000036

+ 249397232 ( 249397232 -      0)      1 allocs BackTraceF3D084C
+       1 (      1 -      0) BackTraceF3D084C allocations

 ntdll!RtlUlonglongByteSwap+00000B52
 MSVCR90!malloc+00000079
 FileGDB!DllCanUnloadNow+0000BB14
 FileGDB!DllCanUnloadNow+0001C6F4
 FileGDB!???+00000000 : 69BC62F5
 FileGDB!???+00000000 : 69BC694A
 RPCRT4!NdrServerInitialize+00000240
 RPCRT4!NdrStubCall2+00000256
 ole32!WdtpInterfacePointer_UserUnmarshal+0000256F
 OLEAUT32!CreateErrorInfo+00000268
 ole32!WdtpInterfacePointer_UserUnmarshal+000025FF
 ole32!WdtpInterfacePointer_UserUnmarshal+00002B59
 ole32!CoTaskMemFree+00001B02
 ole32!CoTaskMemFree+000019F7
 ole32!DcomChannelSetHResult+000008FF
 ole32!WdtpInterfacePointer_UserUnmarshal+00002A56
 ole32!WdtpInterfacePointer_UserUnmarshal+000028CA
 ole32!WdtpInterfacePointer_UserUnmarshal+00002F86
 ole32!DcomChannelSetHResult+0000075C
 ole32!DcomChannelSetHResult+0000071B
 USER32!gapfnScSendMessage+00000332
 USER32!GetThreadDesktop+000000D7
 USER32!CharPrevW+00000138
 USER32!DispatchMessageW+0000000F
 ole32!CoWaitForMultipleHandles+00004311
 ole32!CoWaitForMultipleHandles+000023C1
 ole32!CoWaitForMultipleHandles+00004332
 ole32!CoGetTreatAsClass+00002619
 ole32!CoGetTreatAsClass+0000314B
 KERNEL32!BaseThreadInitThunk+00000012
 ntdll!RtlInitializeExceptionChain+00000063
 ntdll!RtlInitializeExceptionChain+00000036

The total result is

Total increase == 498797272 requested +   -496 overhead = 498796776

Memory was marked just before the call of the InsertFeature code line and after it in the catch code block. I used MessageBox to signal about the mark moments.

I debugged the application in different situations as the different exceptions was get, i.e. compilied against the 3.5 and 4.0 .NET Frameworks and the procedure call in current and concurrent thread. All the times memory usage was increased.

I uploaded the zip with the debug results.

http://dl.dropbox.com/u/91176632/DebugInfo.zip

They also contains lines with <no module> and the "?" signs, that is not good for me, i think.

<no module>!???+00000000 : F13103B
...
MSCTF!???+00000000 : 75931826
...
and so on

I should also note that today i tried to execute the application code from the Add-In for the ArcGlobe app and it succeeded. It makes me to think that the ESRI applications are initialized in a special way or i don't make all the necessary initialization steps in my standalone application to make it work properly. Unfortunately the ArcObjects Help does not contain any information about this.

Re: Insert feature causes Out of memory exception

JasonPike — Sun, 12 Dec 2021 06:53:07 GMT

+ 249397232 ( 249397232 -      0)      1 allocs BackTraceF3D0738
+       1 (      1 -      0) BackTraceF3D0738 allocations

 ntdll!RtlUlonglongByteSwap+00000B52
 MSVCR90!malloc+00000079
 FileGDB!DllRegisterServer+000053E8
 FileGDB!DllCanUnloadNow+0001C5DA
 FileGDB!???+00000000 : 69BC62F5
 FileGDB!???+00000000 : 69BC694A
 RPCRT4!NdrServerInitialize+00000240
 RPCRT4!NdrStubCall2+00000256
 ole32!WdtpInterfacePointer_UserUnmarshal+0000256F
 OLEAUT32!CreateErrorInfo+00000268
 ole32!WdtpInterfacePointer_UserUnmarshal+000025FF
 ole32!WdtpInterfacePointer_UserUnmarshal+00002B59
 ole32!CoTaskMemFree+00001B02
 ole32!CoTaskMemFree+000019F7
 ole32!DcomChannelSetHResult+000008FF
 ole32!WdtpInterfacePointer_UserUnmarshal+00002A56
 ole32!WdtpInterfacePointer_UserUnmarshal+000028CA
 ole32!WdtpInterfacePointer_UserUnmarshal+00002F86
 ole32!DcomChannelSetHResult+0000075C
 ole32!DcomChannelSetHResult+0000071B
 USER32!gapfnScSendMessage+00000332
 USER32!GetThreadDesktop+000000D7
 USER32!CharPrevW+00000138
 USER32!DispatchMessageW+0000000F
 ole32!CoWaitForMultipleHandles+00004311
 ole32!CoWaitForMultipleHandles+000023C1
 ole32!CoWaitForMultipleHandles+00004332
 ole32!CoGetTreatAsClass+00002619
 ole32!CoGetTreatAsClass+0000314B
 KERNEL32!BaseThreadInitThunk+00000012
 ntdll!RtlInitializeExceptionChain+00000063
 ntdll!RtlInitializeExceptionChain+00000036

+ 249397232 ( 249397232 -      0)      1 allocs BackTraceF3D084C
+       1 (      1 -      0) BackTraceF3D084C allocations

 ntdll!RtlUlonglongByteSwap+00000B52
 MSVCR90!malloc+00000079
 FileGDB!DllCanUnloadNow+0000BB14
 FileGDB!DllCanUnloadNow+0001C6F4
 FileGDB!???+00000000 : 69BC62F5
 FileGDB!???+00000000 : 69BC694A
 RPCRT4!NdrServerInitialize+00000240
 RPCRT4!NdrStubCall2+00000256
 ole32!WdtpInterfacePointer_UserUnmarshal+0000256F
 OLEAUT32!CreateErrorInfo+00000268
 ole32!WdtpInterfacePointer_UserUnmarshal+000025FF
 ole32!WdtpInterfacePointer_UserUnmarshal+00002B59
 ole32!CoTaskMemFree+00001B02
 ole32!CoTaskMemFree+000019F7
 ole32!DcomChannelSetHResult+000008FF
 ole32!WdtpInterfacePointer_UserUnmarshal+00002A56
 ole32!WdtpInterfacePointer_UserUnmarshal+000028CA
 ole32!WdtpInterfacePointer_UserUnmarshal+00002F86
 ole32!DcomChannelSetHResult+0000075C
 ole32!DcomChannelSetHResult+0000071B
 USER32!gapfnScSendMessage+00000332
 USER32!GetThreadDesktop+000000D7
 USER32!CharPrevW+00000138
 USER32!DispatchMessageW+0000000F
 ole32!CoWaitForMultipleHandles+00004311
 ole32!CoWaitForMultipleHandles+000023C1
 ole32!CoWaitForMultipleHandles+00004332
 ole32!CoGetTreatAsClass+00002619
 ole32!CoGetTreatAsClass+0000314B
 KERNEL32!BaseThreadInitThunk+00000012
 ntdll!RtlInitializeExceptionChain+00000063
 ntdll!RtlInitializeExceptionChain+00000036

The total result is

Total increase == 498797272 requested +   -496 overhead = 498796776

<no module>!???+00000000 : F13103B
...
MSCTF!???+00000000 : 75931826
...
and so on

Great job! 250MB a pop will get you to an out-of-memory exception very quickly!

The ???? mean that the symbols were unable to be resolved. You can double check to make sure _NT_SYMBOL_PATH is set correctly in your environment variables. It is possible you are behind a firewall that isn't allowing you to access the symbol servers, too. In any case, I was able see some important things without the symbol resolution.

Looking at the code and considering what you've posted (I haven't downloaded your zip from DropBox yet), I think there are two places we can release COM objects and reclaim large chunks of memory. The stacks you posted seem to indicate the majority of the memory is allocated when a GDB is opened, so we need to do one of two things: 1) Release the GDB when we're done with it, 2) reuse the GDB rather than reopening each time.

I want to try #1 first, but I've seen situations where it was impossible to get ArcCatalog to release a connection even when all the references where released.

There are two places that you have references to a GDB:

1) You open a GDB in the Import3DFiles method here:

IWorkspace datasetWorkspace = wsf.OpenFromFile(GDBFilename, 0);

Solution Part 1: Make sure to call Marshal.ReleaseComObject on "datasetWorkspace" at the end of the method

2) You assign it to the property of another COM object later in the Import3DFiles method:

IFieldChecker fieldChecker = new FieldCheckerClass();
IEnumFieldError enumFieldError = null;
IFields validatedFields = null;
fieldChecker.ValidateWorkspace = datasetWorkspace;
fieldChecker.Validate(fcFields, out enumFieldError, out validatedFields);

Solution Part 2: Make sure to call Marshal.ReleaseComObject on "fieldChecker " after the fieldChecker.Validate call.

Try these things and let me know if it reduces the amount of memory being consumed. Use UMDH as you did before and see if some of those stacks go away (you will need to make you second capture after the release statements; hopefully you won't hit the catch block again.) If this doesn't solve the problem, I have some other ideas.

Btw, are you using testFileGDB.gdb in your tests, or a different gdb? How about in the actual command? It looks like you might have a much larger GDB than the one you included in your test code.

Re: Insert feature causes Out of memory exception

JasonPike — Sun, 12 Dec 2021 06:53:10 GMT

I don't know if this will help you or not, but I went ahead and broke your code up into smaller pieces and added some releases.

Also, the forum made me split it into two posts...

        private static IGeometry get_MultiPatchFootprint(IMultiPatch multiPatch)
        {
            IPoint centroid = null;
            IVector3D xVector = null;
            IVector3D zVector = null;
            ITransform2D transformer3D = null;

            try
            {
                centroid = ((IArea)multiPatch).Centroid;
                centroid.Z = 0;

                xVector = new Vector3DClass();
                xVector.SetComponents(10, 0, 0);

                zVector = new Vector3DClass();
                zVector.SetComponents(0, 0, 10);

                transformer3D = (ITransform2D)((ITransform3D)multiPatch).ProjectToPlane(centroid, xVector, zVector);
                transformer3D.Move(centroid.X, centroid.Y);
            }
            finally
            {
                if (zVector != null)
                    Marshal.ReleaseComObject(zVector);

                if (xVector != null)
                    Marshal.ReleaseComObject(xVector);

                if (centroid != null)
                    Marshal.ReleaseComObject(centroid);
            }

            return (IGeometry)transformer3D;
        }

        public static void Import3DFiles(object data)
        {
            ISpatialReference datasetSpatialReference = null;
            ISpatialReference geoSpatialReference = null;
            IFeatureClass objectiveFeatureClass = null;
            IFeatureBuffer featureBuffer = null;
            IFeatureCursor featureCursor = null;

            try
            {
                GetSpatialReferences(out datasetSpatialReference, out geoSpatialReference);

                Array dataArray = (Array)data;
                string GDBFilename = dataArray.GetValue(0).ToString();
                string Dataset = dataArray.GetValue(1).ToString();

                objectiveFeatureClass = GetFeatureClass(GDBFilename, Dataset, datasetSpatialReference);
                ISchemaLock schemaLock = (ISchemaLock)objectiveFeatureClass;
                IFeatureClassLoad featureClassLoad = (IFeatureClassLoad)objectiveFeatureClass;

                schemaLock.ChangeSchemaLock(esriSchemaLock.esriExclusiveSchemaLock);
                featureClassLoad.LoadOnlyMode = true;

                featureBuffer = objectiveFeatureClass.CreateFeatureBuffer();
                featureCursor = objectiveFeatureClass.Insert(true);

                List<GeoReferencedModel> Files = dataArray.GetValue(2) as List<GeoReferencedModel>;
                foreach (GeoReferencedModel geoReferencedModel in Files)
                {
                    InsertModel(geoSpatialReference, datasetSpatialReference, featureBuffer, featureCursor, geoReferencedModel);
                }

                featureCursor.Flush();

                featureClassLoad.LoadOnlyMode = false;
                schemaLock.ChangeSchemaLock(esriSchemaLock.esriSharedSchemaLock);
            }
            finally
            {
                if (featureCursor != null)
                    Marshal.ReleaseComObject(featureCursor);

                if (featureBuffer != null)
                    Marshal.ReleaseComObject(featureBuffer);

                if (objectiveFeatureClass != null)
                    Marshal.ReleaseComObject(objectiveFeatureClass);

                if (datasetSpatialReference != null)
                    Marshal.ReleaseComObject(datasetSpatialReference);

                if (geoSpatialReference != null)
                    Marshal.ReleaseComObject(geoSpatialReference);
            }

        }

        private static void GetSpatialReferences(out ISpatialReference spatialReference, out ISpatialReference geoSR)
        {
            ISpatialReferenceFactory3 srFactory = null;
            IVerticalDatum verticalDatum = null;
            ILinearUnit unit = null;
            IVerticalCoordinateSystemEdit vcsEdit = null;

            try
            {
                srFactory = new SpatialReferenceEnvironmentClass();
                IProjectedCoordinateSystem pcs = srFactory.CreateProjectedCoordinateSystem(32639);

                spatialReference = (ISpatialReference)pcs;
                ISpatialReferenceResolution srResolution = (ISpatialReferenceResolution)spatialReference;
                srResolution.ConstructFromHorizon();
                srResolution.SetDefaultMResolution();
                srResolution.SetDefaultXYResolution();
                srResolution.SetDefaultZResolution();

                ISpatialReferenceTolerance srTolerance = (ISpatialReferenceTolerance)spatialReference;
                srTolerance.SetDefaultMTolerance();
                srTolerance.SetDefaultXYTolerance();
                srTolerance.SetDefaultZTolerance();

                verticalDatum = srFactory.CreateVerticalDatum((int)esriSRVerticalDatumType.esriSRVertDatum_SeaLevel);
                IHVDatum hvDatum = verticalDatum as IHVDatum;
                unit = srFactory.CreateUnit((int)esriSRUnitType.esriSRUnit_Meter) as ILinearUnit;
                vcsEdit = (IVerticalCoordinateSystemEdit)new VerticalCoordinateSystemClass();
                int positive = 1;
                double shift = 0;
                vcsEdit.DefineEx("", "", "", "", "", hvDatum, unit, ref shift, ref positive);
                ((ISpatialReference3)spatialReference).VerticalCoordinateSystem = (IVerticalCoordinateSystem)vcsEdit;
                ISpatialReferenceResolution sprefResolution = (ISpatialReferenceResolution)spatialReference;
                sprefResolution.SetDefaultZResolution();
                srTolerance = (ISpatialReferenceTolerance)spatialReference;
                srTolerance.SetDefaultZTolerance();
                spatialReference.Changed();

                IGeographicCoordinateSystem gcs = srFactory.CreateGeographicCoordinateSystem(4326);
                geoSR = (ISpatialReference)gcs;
                srResolution = (ISpatialReferenceResolution)geoSR;
                srResolution.ConstructFromHorizon();
                srResolution.SetDefaultMResolution();
                srResolution.SetDefaultXYResolution();
                srResolution.SetDefaultZResolution();
                srTolerance = (ISpatialReferenceTolerance)geoSR;
                srTolerance.SetDefaultMTolerance();
                srTolerance.SetDefaultXYTolerance();
                srTolerance.SetDefaultZTolerance();
            }
            finally
            {
                if (vcsEdit != null)
                    Marshal.ReleaseComObject(vcsEdit);

                if (unit != null)
                    Marshal.ReleaseComObject(unit);

                if (verticalDatum != null)
                    Marshal.ReleaseComObject(verticalDatum);

                if( srFactory != null )
                    Marshal.ReleaseComObject(srFactory);
            }
        }

        private static void InsertModel(ISpatialReference geoSR, ISpatialReference DatasetSpatialReference, IFeatureBuffer featureBuffer, IFeatureCursor featureCursor, GeoReferencedModel geoReferencedModel)
        {
            IGeometry multiPatch = null;
            IPoint placement = null;
            IGeometry footprint = null;

            try
            {
                //reading lat,long and other values values from files with own SketchUpReader (for *.skp) and ZipForge, XDocument (for *.kmz)
                //do not use any ArcObjects
                placement = geoReferencedModel.get_Placement();
                placement.SpatialReference = geoSR;
                ((IZAware)placement).ZAware = true;
                placement.Project(DatasetSpatialReference);

                //get Z value from IFunctionalSurface (relief raster)
                placement.Z = 0; //just for test

                if (!placement.Z.Equals(double.NaN))
                {
                    multiPatch = geoReferencedModel.get_MultiPatch(placement, DatasetSpatialReference);

                    if (multiPatch != null)
                    {
                        //here i compute a footprint of multipatch and store it in another featureclass 
                        footprint = get_MultiPatchFootprint((IMultiPatch)multiPatch);
                        featureBuffer.Shape = multiPatch;
                        featureCursor.InsertFeature(featureBuffer);
                    }
                }
            }
            finally
            {
                if (footprint != null)
                    Marshal.ReleaseComObject(footprint);

                if (multiPatch != null)
                    Marshal.ReleaseComObject(multiPatch);

                if (placement != null)
                    Marshal.ReleaseComObject(placement);
            }
        }

Re: Insert feature causes Out of memory exception

JasonPike — Sun, 12 Dec 2021 06:53:13 GMT

Here is part 2:

        private static IFeatureClass GetFeatureClass(string GDBFilename, string Dataset, ISpatialReference DatasetSpatialReference)
        {
            IWorkspaceFactory wsf = null;
            IWorkspace datasetWorkspace = null;
            IFeatureClass objectiveFeatureClass = null;

            try
            {
                wsf = new FileGDBWorkspaceFactoryClass();
                datasetWorkspace = wsf.OpenFromFile(GDBFilename, 0);

                if (!((IWorkspace2)datasetWorkspace).get_NameExists(esriDatasetType.esriDTFeatureClass, Dataset))
                    objectiveFeatureClass = CreateFeatureClass(Dataset, DatasetSpatialReference, datasetWorkspace);
                else
                    objectiveFeatureClass = ((IFeatureWorkspace)datasetWorkspace).OpenFeatureClass(Dataset);

            }
            finally
            {
                if( wsf != null )
                    Marshal.ReleaseComObject(wsf);

                if( datasetWorkspace != null )
                    Marshal.ReleaseComObject(datasetWorkspace);
            }    

            return objectiveFeatureClass;
        }

        private static IFeatureClass CreateFeatureClass(string Dataset, ISpatialReference DatasetSpatialReference, IWorkspace datasetWorkspace)
        {
            IFeatureClass objectiveFeatureClass = null;
            IField shapeField = null;
            IGeometryDef geometryDef = null;
            IField oidField = null;
            IFields fcFields = null;
            IEnumFieldError enumFieldError = null;
            IFields validatedFields = null;
            IFieldChecker fieldChecker = null;
            IObjectClassDescription objectDescription = null;

            try
            {
                shapeField = new FieldClass();
                IFieldEdit fieldEdit = (IFieldEdit)shapeField;
                fieldEdit.Name_2 = "Shape";
                fieldEdit.Type_2 = esriFieldType.esriFieldTypeGeometry;

                geometryDef = new GeometryDefClass();
                IGeometryDefEdit geometryDefEdit = (IGeometryDefEdit)geometryDef;
                geometryDefEdit.GeometryType_2 = esriGeometryType.esriGeometryMultiPatch;
                geometryDefEdit.GridCount_2 = 1;
                geometryDefEdit.set_GridSize(0, 0);
                geometryDefEdit.HasZ_2 = true;
                geometryDefEdit.HasM_2 = false;
                geometryDefEdit.SpatialReference_2 = (DatasetSpatialReference != null) ? DatasetSpatialReference : geometryDefEdit.SpatialReference_2 = new UnknownCoordinateSystemClass();
                fieldEdit.GeometryDef_2 = geometryDef;

                oidField = new FieldClass();
                fieldEdit = (IFieldEdit)oidField;
                fieldEdit.Name_2 = "OID";
                fieldEdit.Type_2 = esriFieldType.esriFieldTypeOID;
                fieldEdit.Precision_2 = 0;

                fcFields = new FieldsClass();
                IFieldsEdit fcFieldsEdit = (IFieldsEdit)fcFields;
                fcFieldsEdit.AddField(shapeField);
                fcFieldsEdit.AddField(oidField);

                fieldChecker = new FieldCheckerClass();
                fieldChecker.ValidateWorkspace = datasetWorkspace;
                fieldChecker.Validate(fcFields, out enumFieldError, out validatedFields);

                objectDescription = new FeatureClassDescriptionClass();

                objectiveFeatureClass = ((IFeatureWorkspace)datasetWorkspace).CreateFeatureClass(
                    Dataset,
                    validatedFields,
                    null,
                    objectDescription.ClassExtensionCLSID,
                    esriFeatureType.esriFTSimple,
                    shapeField.Name,
                    "");
            }
            finally
            {
                if (shapeField != null)
                    Marshal.ReleaseComObject(shapeField);

                if (geometryDef != null)
                    Marshal.ReleaseComObject(geometryDef);

                if (oidField != null)
                    Marshal.ReleaseComObject(oidField);

                if (fcFields != null)
                    Marshal.ReleaseComObject(fcFields);

                if (enumFieldError != null)
                    Marshal.ReleaseComObject(enumFieldError);

                if (validatedFields != null)
                    Marshal.ReleaseComObject(validatedFields);

                if (fieldChecker != null)
                    Marshal.ReleaseComObject(fieldChecker);

                if (objectDescription != null)
                    Marshal.ReleaseComObject(objectDescription);
            }
            return objectiveFeatureClass;
        }
    }

Re: Insert feature causes Out of memory exception

MarcinDruzgala — Sun, 12 Dec 2021 06:53:15 GMT

Here is part 2:

        private static IFeatureClass GetFeatureClass(string GDBFilename, string Dataset, ISpatialReference DatasetSpatialReference)
        {
            IWorkspaceFactory wsf = null;
            IWorkspace datasetWorkspace = null;
            IFeatureClass objectiveFeatureClass = null;

            try
            {
                wsf = new FileGDBWorkspaceFactoryClass();
                datasetWorkspace = wsf.OpenFromFile(GDBFilename, 0);

                if (!((IWorkspace2)datasetWorkspace).get_NameExists(esriDatasetType.esriDTFeatureClass, Dataset))
                    objectiveFeatureClass = CreateFeatureClass(Dataset, DatasetSpatialReference, datasetWorkspace);
                else
                    objectiveFeatureClass = ((IFeatureWorkspace)datasetWorkspace).OpenFeatureClass(Dataset);

            }
            finally
            {
                if( wsf != null )
                    Marshal.ReleaseComObject(wsf);

                if( datasetWorkspace != null )
                    Marshal.ReleaseComObject(datasetWorkspace);
            }    

            return objectiveFeatureClass;
        }

        private static IFeatureClass CreateFeatureClass(string Dataset, ISpatialReference DatasetSpatialReference, IWorkspace datasetWorkspace)
        {
            IFeatureClass objectiveFeatureClass = null;
            IField shapeField = null;
            IGeometryDef geometryDef = null;
            IField oidField = null;
            IFields fcFields = null;
            IEnumFieldError enumFieldError = null;
            IFields validatedFields = null;
            IFieldChecker fieldChecker = null;
            IObjectClassDescription objectDescription = null;

            try
            {
                shapeField = new FieldClass();
                IFieldEdit fieldEdit = (IFieldEdit)shapeField;
                fieldEdit.Name_2 = "Shape";
                fieldEdit.Type_2 = esriFieldType.esriFieldTypeGeometry;

                geometryDef = new GeometryDefClass();
                IGeometryDefEdit geometryDefEdit = (IGeometryDefEdit)geometryDef;
                geometryDefEdit.GeometryType_2 = esriGeometryType.esriGeometryMultiPatch;
                geometryDefEdit.GridCount_2 = 1;
                geometryDefEdit.set_GridSize(0, 0);
                geometryDefEdit.HasZ_2 = true;
                geometryDefEdit.HasM_2 = false;
                geometryDefEdit.SpatialReference_2 = (DatasetSpatialReference != null) ? DatasetSpatialReference : geometryDefEdit.SpatialReference_2 = new UnknownCoordinateSystemClass();
                fieldEdit.GeometryDef_2 = geometryDef;

                oidField = new FieldClass();
                fieldEdit = (IFieldEdit)oidField;
                fieldEdit.Name_2 = "OID";
                fieldEdit.Type_2 = esriFieldType.esriFieldTypeOID;
                fieldEdit.Precision_2 = 0;

                fcFields = new FieldsClass();
                IFieldsEdit fcFieldsEdit = (IFieldsEdit)fcFields;
                fcFieldsEdit.AddField(shapeField);
                fcFieldsEdit.AddField(oidField);

                fieldChecker = new FieldCheckerClass();
                fieldChecker.ValidateWorkspace = datasetWorkspace;
                fieldChecker.Validate(fcFields, out enumFieldError, out validatedFields);

                objectDescription = new FeatureClassDescriptionClass();

                objectiveFeatureClass = ((IFeatureWorkspace)datasetWorkspace).CreateFeatureClass(
                    Dataset,
                    validatedFields,
                    null,
                    objectDescription.ClassExtensionCLSID,
                    esriFeatureType.esriFTSimple,
                    shapeField.Name,
                    "");
            }
            finally
            {
                if (shapeField != null)
                    Marshal.ReleaseComObject(shapeField);

                if (geometryDef != null)
                    Marshal.ReleaseComObject(geometryDef);

                if (oidField != null)
                    Marshal.ReleaseComObject(oidField);

                if (fcFields != null)
                    Marshal.ReleaseComObject(fcFields);

                if (enumFieldError != null)
                    Marshal.ReleaseComObject(enumFieldError);

                if (validatedFields != null)
                    Marshal.ReleaseComObject(validatedFields);

                if (fieldChecker != null)
                    Marshal.ReleaseComObject(fieldChecker);

                if (objectDescription != null)
                    Marshal.ReleaseComObject(objectDescription);
            }
            return objectiveFeatureClass;
        }
    }

I have to ask because I'm very curious about this, when you are releasing COM objects you always do something like this:

try
{
 row = cursor.NextRow();
 while(row != null)
 {
  //some logic
  Marshal.ReleaseComObject(row)
  row = null;
  row = cursor.NextRow();
 }
}
finally
{
 if(row =! null)
  Marshal.ReleaseComObject(row);
 Marshal.ReleaseComObject(cursor);
}

Now let's analyze this, in loop you are releasing the row object every time and assinging it's value to null - because as you said/wrote somewhere you want to make sure the row object will be destroyed/released. But what about the finally section: if the row object is not null you are releasing it by ReleaseComObject method...but the ReleaseComObject method only decreases the amount of references by 1, so there is a slight possibility that a row object won't be released completely, right? Should we use the FinalReleaseComObject method then? I know that your code examples for releasing COM objects are helping but I'm just willing to learn as much as I can, since COM objects generate so much problems for .net developers in esri products.

Regards,
MDruzgala