[fdo-trac] #284: .NET: Exceptions being thrown on IInserts/IUpdates
involving large datasets
FDO
trac_fdo at osgeo.org
Fri Mar 28 05:13:28 EDT 2008
#284: .NET: Exceptions being thrown on IInserts/IUpdates involving large datasets
-----------------------+----------------------------------------------------
Reporter: MaksimS | Owner: gregboone
Type: defect | Status: new
Priority: major | Milestone: 3.3.1
Component: FDO API | Version: 3.2.0
Severity: 3 | Keywords:
External_id: |
-----------------------+----------------------------------------------------
Managed wrapper seems to throw an error while performing perpetual
IInserts/IUpdates involving large datasets (i.e. tens of thousands of
feature instances). This keeps happening since god-knows-when, but let's
set it to version 3.2.0 (continued to appear in 3.3.0 also).
Exception being thrown:
{{{
- 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.
}}}
There are also other types of exceptions fired here and there, scattered
among other related projects (i.e. MapGuide) - possibly related to this:
[http://trac.osgeo.org/mapguide/ticket/323]
It's general opinion (me, Clayton) that something's buggy with managed
wrapper and garbage collector - it's not disposing its underlying
unmanaged resources in the correct order. As Clayton correctly pointed
out: "...and that this problem will occur when the garbage collector comes
around - hence the pseudo-randomness...", therefor a fuzziness on properly
pinpointing source of the problem.
--
Ticket URL: <http://trac.osgeo.org/fdo/ticket/284>
FDO <http://fdo.osgeo.org/>
Feature Data Objects
More information about the fdo-trac
mailing list