1

I am reading now about the Dispose and the Finalize method on the CLR ( 4.0 ) I dont understand something ...

If I add an implementation of Finalize ( ~className1 ) to my code => then the Finalize List have pointer to the object instance that in the managed heap.

Now, Lets say i did not implement the Finalize ( ~className2 ) and i just implemented the IDisposable interface on my code - Is thie object will have pointer from the Finalize List ?

Antony Scott
  • 21,690
  • 12
  • 62
  • 94
Yanshof
  • 9,659
  • 21
  • 95
  • 195

2 Answers2

2

No. If an object doesn't have a finalizer, it will not be in the finalize queue.

Reference: MSDN

The garbage collector keeps track of objects that have Finalize methods... Each time your application creates an object that has a Finalize method, the garbage collector places an entry in the finalization queue that points to that object.

Paul Phillips
  • 6,093
  • 24
  • 34
  • But is the Dispose is call to the Finalize method or just make the 'cleanup' of the object ? – Yanshof Feb 06 '12 at 23:43
  • 1
    @Yanshof The finalize method calls `Dispose`, not the other way around. There is no way to actually call the finalize method. [This answer explains the IDisposable implementation pattern in depth.](http://stackoverflow.com/a/898867/461968) – Paul Phillips Feb 06 '12 at 23:50
0

Basically, the longer an object exists, the less the garbage collector will check whether it's still referenced in the code. That means that unused objects can often still be in memory although they haven't been referenced anymore for a long time. Also, if you want to explicitly tell an object to clean up its resources, use the Dispose method. I'd suggesst calling GC.SuppressFinalize(this) in its implementation, and calling the Dispose method in the finalizer as well. That way, if the user forgets to call Dispose, which should not but can happen, the object's resources will get freed-up eventually.

haiyyu
  • 2,194
  • 6
  • 22
  • 34