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

[Maksim Sestic]

What I meant was FDO stability when sharing results between threads. Running
it on a single thread alone wouldn't pose a problem I guess. But what if I
return instantiated IFeatureReader (what else?) back from the worker thread
to a main one?


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Carl Jokl
Sent: Tuesday, July 15, 2008 11:10
To: fdo-internals at lists.osgeo.org
Subject: RE: [fdo-internals] SDF 3.0 FDO Provider Serious Memory Leak


My benchmark application has the benchmark code including FDO work running
on it's own thread to prevent locking up the GUI while the test ran. That in
itself did not seem to cause a problem.

--
View this message in context:
http://www.nabble.com/SDF-3.0-FDO-Provider-Serious-Memory-Leak-tp18447913p18
460924.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

__________ NOD32 3267 (20080714) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com