Why is it preferred to not use finalize for clean up
Why is it preferred to not use finalize for clean up?
Problem with finalize is that garbage collection has to make two rounds in order to remove
objects which have finalize methods.
Below figure will make things clear regarding the two rounds of garbage collection rounds performed for the objects having finalized methods.
In this scenario there are three objects Object1, Object2 and Object3. Object2 has the finalize method overridden and remaining objects do not have the finalize method overridden.
Now when garbage collector runs for the first time it searches for objects whose memory has to free. He can see three objects but only cleans the memory for Object1 and Object3. Object2 it pushes to the finalization queue.
Now garbage collector runs for the second time. He see’s there are no objects to be released and then checks for the finalization queue and at this moment it clears object2 from the memory.
So if you notice that object2 was released from memory in the second round and not first. That’s why the best practice is not to write clean up Non.NET resources in Finalize method rather use the DISPOSE.
2007-10-23, 6103👍, 0💬
Is Session_End event supported in all session modes ? Session_End event occurs only in “Inproc mode”...
How Do I Run JUnit Tests from Command Window? To run JUnit tests from a command window, you need to ...
How To Retrieve the Count of Updated Rows? - Oracle DBA FAQ - Working with Database Objects in PL/SQ...
Managed Code and Unmanaged Code related ASP.NET - How do you hide Public .NET Classes and other publ...
What are database triggers? How are the triggers fired? Read this collection of questions and answer...