[fdo-users] .net Wrapper quirks
jackie.ng at aecsystems.com.au
Fri Apr 4 02:37:58 EDT 2008
I just looked at the unit test code for the ticket, and noticed I might have
been doing something wrong.
I forgot that IInsert::Execute() returns an IFeatureReader and so I haven't
been closing and disposing them.
One (of many?) possible cause(s)?
Jackie Ng wrote:
> Hi All,
> I've been writing .net code that copies data from one FDO connection to
> another (Doing a series of IInsert::Execute() calls from an IFeatureReader
> ). In my adventures using the FDO .net wrapper, I have encountered the
> following problems at random:
> - System.AccessViolationExceptions ("Attempted to read or write protected
> memory. This is often an indication that other memory is corrupt") thrown
> at OSGeo.FDO.Runtime.Disposable.Finalize() (Target Site: void
> ReleaseUnmanagedObject() )
> - C++ pure virtual function call errors.
> - Memory allocation failed errors.
> Is there some quirks with the .net wrapper that I should be aware of? As
> OSGeo.FDO.Runtime.Disposable implements IDisposable, I've been wrapping
> nearly every FDO object used inside using() blocks. Could this be a cause?
> I am using .net wrappers for FDO 3.3.0
> - Jackie
View this message in context: http://www.nabble.com/.net-Wrapper-quirks-tp16318694s18162p16485877.html
Sent from the fdo-users mailing list archive at Nabble.com.
More information about the fdo-users