About Finalize Method

Avoid writing a Finalize method for the following reasons :

Finalizable objects take longer to allocate because pointers to them must be placed on the finalization list.
Finalizable objects get promoted to older generations, which increases memory pressure and prevents the object's memory from being collected at the time the garbate collector determines that the object is garbage. In addition, all objects referred to directly or inderectly by this object get promoted as well.
Finalizable objects cause your application to run slower since extra processing must occur for each object when collected.

Writing Finalize method to release managed resources actually adds overheads on the CLR at object construction and collection. Plus, you can't control when the Finalize method will execute. If you stop writing Finalize method in your class, your code will be simpler and performance will be better.

1 Reply

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

Niradhip Chakraborty17y ago
Avoid writing a Finalize method for the following reasons :
- Finalizable objects take longer to allocate because pointers to them must be placed on the finalization list.
- Finalizable objects get promoted to older generations, which increases memory pressure and prevents the object's memory from being collected at the time the garbate collector determines that the object is garbage. In addition, all objects referred to directly or inderectly by this object get promoted as well.
- Finalizable objects cause your application to run slower since extra processing must occur for each object when collected.
Writing Finalize method to release managed resources actually adds overheads on the CLR at object construction and collection. Plus, you can't control when the Finalize method will execute. If you stop writing Finalize method in your class, your code will be simpler and performance will be better.