Dataset copy() memory leak

Hi there,

If your working with C# and .net then you cannot force the garbage collector and thus disposing of the back-up dataset is pending....and so is your memory allocation.

Now if you have to backup frequently I suggest an embedded database and creating a backup routine according to your wishes... and thus not using more memory than needed.

And if you fine tune your backup routine to working with dataset.GetChanges(), the transaction wil be even faster..

And if you don't wanna have an embedded database all pre-made, why not add, create "scheme deffinitions" on the fly.

I hope this helped
grtz

Well you can request the Garbage collector to run garbage collection process by

GC.Collect();
GC.WaitForPendingFinalizers();

This doesn't guarentee the memory to be cleaned up immediately because of GC's own algo and flow plus this is not recommended because and garbage collection is a costly process as it has to check every thing marked as disposed and after cleaning up it re-position all in-memory objects sequally.

here is the link:
http://msdn.microsoft.com/en-us/library/system.gc.waitforpendingfinalizers.aspx[^]

Thanks,
Hemant

You're probably looking in Task Manager to see the memory usage of your application. DON'T!

.NET applications, like Java, run in a virtual execution environment. Task Manager is showing you the memory that is RESERVED for your applications environment, not how much your app is actually using.

Use PerfMon and the .NET Memory counters to see how much your app is actually using.

The .NET CLR maintains a managed heap of memory that it uses to allocate objects that your application creates. When you're no long using those objects, the memory gets returned back to the managed heap, not to Windows. Task Manager is showing you that size of that managed heap, among other things.

If Windows runs low on memory, the .NET CLR does a very good job of managing its heap and will return memory back to Windows whenever Windows wants it.