What method should use to control object overflow in GC ?

Sandeep .Net Framework by default manage garbage collection for managed objects. Garbage collector regularly maintaining cleaning Gen0, Gen1 & Gen2.

GC works only for managed resources, therefore .NET provide Dispose and Finalize to release unmanaged resources like stream, database connection, COM objects etc. If your application having expensive external resources ten you can explicitly release the resource before the garbage collector frees the object or memory leak occur.

1) Dispose

Dispose must be called explicitly for types which implements IDisposable. You must call this either using Dispose() or via Using construct. Use GC.SuppressFinalize(this) to prevent call to Finalizer if you have already used dispose().

2) Finalize or Distructor

It is called implicitly after object is eligible for cleanup, finalizer for objects are called sequentially by finalizer thread. Drawback of implementing finalizer is that it memory reclaim gets delayed as finalizer for such class/types must be called prior clean up, so an additional collect to reclaim memory.

3) GC.Collect()

Using GC.Collect() doesn't necessarily put GC for collection, GC can still override and run whenever it wants to. Also GC.Collect() will only run the tracing portion of garbage collection and add items to finalizer queue but not call finalizers for the types, that is handled by another thread. Use WaitForPendingFinalizers if you want to make sure all finalizers have been called after you invoke GC.Collect().

If this is helpful for you then please accept my Answer.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Sujeet Suman10y ago
Sandeep .Net Framework by default manage garbage collection for managed objects. Garbage collector regularly maintaining cleaning Gen0, Gen1 & Gen2.

GC works only for managed resources, therefore .NET provide Dispose and Finalize to release unmanaged resources like stream, database connection, COM objects etc. If your application having expensive external resources ten you can explicitly release the resource before the garbage collector frees the object or memory leak occur.

1) Dispose
Dispose must be called explicitly for types which implements IDisposable. You must call this either using Dispose() or via Using construct. Use GC.SuppressFinalize(this) to prevent call to Finalizer if you have already used dispose().

2) Finalize or Distructor
It is called implicitly after object is eligible for cleanup, finalizer for objects are called sequentially by finalizer thread. Drawback of implementing finalizer is that it memory reclaim gets delayed as finalizer for such class/types must be called prior clean up, so an additional collect to reclaim memory.

3) GC.Collect()
Using GC.Collect() doesn't necessarily put GC for collection, GC can still override and run whenever it wants to. Also GC.Collect() will only run the tracing portion of garbage collection and add items to finalizer queue but not call finalizers for the types, that is handled by another thread. Use WaitForPendingFinalizers if you want to make sure all finalizers have been called after you invoke GC.Collect().

If this is helpful for you then please accept my Answer.
0