[fdo-users] RE: Re:
ray.wu at efacec.com
Fri Mar 4 17:50:09 EST 2011
From: Ray [via OSGeo.org]
[mailto:ml-node+6090344-1756139584-304287 at n2.nabble.com]
Sent: Friday, March 04, 2011 5:48 PM
To: Ray Wu
Subject: Re: Re:
Using your strategy, the "Attemp to read/write to protected memory"
issue became better and it actually improved the performance for
importing big dataset. However, when I test with a very big dataset (10
hr importing time), I got a new problem "(dbgql_define_rdb) Memory Error
when call FDOCmd.Execute()" which I posted on this website a few weeks
ago. If I don't use the dictionary strategy, the memory error is not
I wonder if the new memory issue could be related with memory cleanup of
FDO objects. I suspect it might be related with GeometryValue cleanup.
When I tried to use GeometryValue.Dispose(), I got "Attemp to read/write
to protected memory" again. I wonder how do you clean GeometryValue
object when using dictionary strategy and set geometry for each new
If you reply to this email, your message will be added to the discussion
To unsubscribe from "Attemp to read/write to protected memory" exception
when reusing fdo command, click here
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Attemp-to-read-write-to-protected-memory-exception-when-reusing-fdo-command-tp5766778p6090355.html
Sent from the FDO Users mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fdo-users