[Solved] Why is relying on the finalize() method for resource cleanup considered a bad practice in Java? — Ans: Because finalize() execution timing is unpredictable and may never run | Java

Java - Classes and Objects

Why is relying on the finalize() method for resource cleanup considered a bad practice in Java?

ABecause <code>finalize()</code> is called multiple times per object

BBecause <code>finalize()</code> runs immediately after object creation

CBecause <code>finalize()</code> prevents garbage collection

DBecause <code>finalize()</code> execution timing is unpredictable and may never run

Step-by-Step Solution

Solution:

Step 1: Understand finalize() behavior
The finalize() method is called by the garbage collector but its timing is unpredictable and may never be called.
Step 2: Clarify misconceptions
It does not run immediately after creation, does not prevent GC, and is called at most once per object.
Final Answer:
Because finalize() execution timing is unpredictable and may never run -> Option D
Quick Check:
finalize() timing unpredictable = A [OK]

Quick Trick: finalize() is unreliable for cleanup, avoid using it [OK]

Common Mistakes:

Master "Classes and Objects" in Java

9 interactive learning modes - each teaches the same concept differently

More Java Quizzes

Why is relying on the finalize() method for resource cleanup considered a bad practice in Java?