[fdo-internals] SDF 3.0 FDO Provider Serious Memory Leak

Traian Stanev traian.stanev at autodesk.com
Mon Jul 14 12:48:41 EDT 2008

I take it your testing code uses the managed API?


> -----Original Message-----
> From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-
> bounces at lists.osgeo.org] On Behalf Of Carl Jokl
> Sent: Monday, July 14, 2008 12:46 PM
> To: fdo-internals at lists.osgeo.org
> Subject: [fdo-internals] SDF 3.0 FDO Provider Serious Memory Leak
> I don't know if anyone else has encountered severe memory usage
> problems when
> using the SDF FDO Provider?
> The issue has come up with testing code. When reading data from a 344MB
> 3.0 file memory usage peaks at 427mb (more than the size of the SDF
> file
> itself which is pretty poor to say the least). What is perhaps more
> worrying
> though is that even after closing and disposing of all readers (even
> setting
> them to null afterwards) and FDO connections and even if explicitly
> calling
> garbage collection about 340mb of ram never gets released.
> Problems have happened when migrating data  using FDO where the CLI has
> run
> out of memory.
> If there is a memory leak of some kind of this magnitude it is
> extremely
> worrying in terms of the practicalities of running a MapGuide server
> using
> FDO if the amount of memory used could just keep spiraling over time
> until
> the server eventually runs out.
> Has this issue been seen and is there anything which can be done about
> it?
> --
> View this message in context: http://www.nabble.com/SDF-3.0-FDO-
> Provider-Serious-Memory-Leak-tp18447913p18447913.html
> Sent from the FDO Internals mailing list archive at Nabble.com.
> _______________________________________________
> fdo-internals mailing list
> fdo-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-internals

More information about the fdo-internals mailing list