MapForums

Hi all,

Each time I call the below VB.NET code the memory usage of MapPoint increases up to 1-2mb. This continues to increase until around 90-100mb when the application dies. The only way I have been able to prevent this is to completely create and destroy the mappoint object for every time I want to perform a region check on a location check (very slow obviously). The best solution would be to keep the mappoint application persistent (with map/shapes loaded) and then do a location check.

Has anyone else had this issue or found a solution to the memory problem?

Thanks!

oLocation = oMap.FindAddress(Street, City, State, Zip, MapPoint.GeoCountry.geoCountryUnitedStates)
If Not oLocation Is Nothing Then
oPushpin = oMap.AddPushpin(oLocation, "Home")

For Each mShape In oMap.Shapes
If mShape.Type < MapPoint.GeoShapeType.geoLine Then
For Each mData In oMap.DataSets
mRst = mData.QueryShape(mShape)
mRst.MoveFirst()
Do While mRst.EOF = False
If mRst.Location.StreetAddress.Value = oLocation.StreetAddress.Value Then
Console.WriteLine("Senate District: " & mShape.Name)
If sDistrict = "" Or sDistrict = "SD1" Then
sDistrict = mShape.Name
End If
Exit For
End If
mRst.MoveNext()
Threading.Thread.Sleep(1)
Loop
mRst = Nothing
mData = Nothing
Next mData
End If
Next mShape
oPushpin.Delete()
oPushpin = Nothing
oLocation = Nothing
End If
oMap.Saved = True
GC.Collect()
Return sDistrict

Just discovered that this only happens in the VB.NET version and not in VB6. Probably a bug in the interop DLL or something... how does one go about reporting this as a bug to MS?

Well it turns out that to properly dispose of COM objects in .NET you cannot simply use the = Nothing statement. You must first use ReleaseComObject(oObject) and then set the object to nothing. An article is at http://support.microsoft.com/default...;EN-US;Q317109.

So now you know ;-)

P.S. Been real nice talking to myself on this forum ;-)