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, 6699👍, 0💬
How To Run "mysql" Commands from a Batch File? - MySQL FAQs - Command-Line End User Interface mysql ...
What is the result of using Option Explicit? When writing your C program, you can include files in t...
What does a special set of tags <?= and ?> do in a PHP script page? <?= express...
How To Empty Your Recycle Bin? - Oracle DBA FAQ - Managing Oracle Database Tables If your recycle bi...
Rachel opened her math book and found that the sum of the facing pages was 245. What pages did she o...