[fdo-internals] SDF 3.0 FDO Provider Serious Memory Leak
Kenneth Skovhede, GEOGRAF A/S
ks at geograf.dk
Tue Jul 15 05:18:11 EDT 2008
I just tried looking over the code, but I can't remember what particularly
made it useable for large tables.
I do recall that the initial version of my code could not handle more than
3000 records before throwing an "Out of memory" error, masked as
a "Protected read/write error"
Regards, Kenneth Skovhede, GEOGRAF A/S
Maksim Sestic skrev:
> I'm doing this too, but there are situations when you simply cannot trust
> FDO managed wrappers, neither nor you can rely on common object reusability
> See trac #356: .NET: IFeatureReader throws errors when passed by value
> BTW, described minimize-restore main window trick works if FDO connection
> runs on the same thread as the main application. I didn't try running FDO on
> separate dedicated thread since noone can guarantee it's stability, but I
> might experiment with this a bit if I find some time.
> Kenneth, what FDO classes did you find suitable for reuse?
> Maksim Sestic
More information about the fdo-internals