Hi Tim,

I've emailed you a separate email with a sample project attached to demonstrate the problem.

It seems that when creating a EDBDataAdapter object, the EDB engine implicitly creates an EDBCommand object and attaches it to the Adapter.SelectCommand, but this doesn't get Disposed correctly.

Please run the sample application, open up Task Manager (go to "Processes" to see the Memory consumption).

Now click the TEST button a few time. All it's doing is filling a DataTable. As you'll see, the memory just keeps going up. I used .NET Memory Profiler and it seems that there's a whole raft of EDBxxxxx objects which are hanging around in an "undisposed" state and aren't being Garbage Collected.

Now if you enable the two lines of code to dispose of the Adapter.SelectCommand object and repeat the above. .NET Memory Profiler now shows the objects are being GC'd correctly and the memory is freed as you can see in Task Manager.

I noticed this problem when users started getting "Out of Memory" errors with our since upgrading from 2.03b24 to 2.04b4.

Hope this helps and hope for a speedy fix - thanks!

Hedley

Hedley,

<< I've emailed you a separate email with a sample project attached to
demonstrate the problem. >>

Thanks - looking into this.

--
Tim Young
Elevate Software
www.elevatesoft.com