Understanding the Finalize Method in Java
📌 The `finalize()` method is discussed as a mechanism related to Garbage Collection, following the lecture on garbage collection (Lecture 48).
📌 When an object is created using the `new` keyword, it receives dynamic memory, and its constructor initializes its members, which may point to external resources like printers, files, or databases.
📌 When an object becomes unreachable (a "garbage block") after its reference variable goes out of scope, the JVM's Garbage Collector (GC) is responsible for releasing its memory.

Purpose and Execution of `finalize()`
📌 The primary utility of `finalize()` is to perform cleanup operations just before an object's memory is released by the GC, similar to a destructor in C++.
📌 Cleanup operations include properly closing database connections or ensuring data is written to a hard disk before the external resource pointers inside the object are destroyed.
📌 The GC thread calls the object's `finalize()` method only once immediately before sweeping out (destroying) the object.

Inheritance and Calling `finalize()`
📌 Every Java class is a descendant of the `Object` class, which contains a default, empty `finalize()` method.
📌 If a subclass does not override `finalize()`, the GC will call the version inherited from the `Object` class, which performs no action.
📌 Unlike C++, there is no automatic chaining of `finalize()` methods in Java; the subclass `finalize()` does not automatically call the superclass's `finalize()`—it must be called explicitly using `super.finalize()`.

Forced Execution and Reliability
➡️ Developers can call `finalize()` manually like any other method (e.g., using `Runtime.getRuntime().runFinalization()`), but this does not guarantee the object's memory release; only the GC triggers memory release.
➡️ Exceptions occurring inside the `finalize()` method are ignored by the Garbage Collector, ensuring the GC continues its process and destroys the object.
➡️ Relying on forced execution is not recommended as it is not reliable; execution is only guaranteed when the GC runs.

Key Points & Insights
➡️ `finalize()` serves as the object's "last wish" to execute critical closing/cleanup code before memory reclamation by the GC.
➡️ If an object holds external resources (e.g., database connections), ensure the code to close these is placed within the `finalize()` method to prevent resource leaks.
➡️ Do not depend on manual execution of `finalize()`; trust the Garbage Collector for invoking cleanup logic just before memory destruction.

📸 Video summarized with SummaryTube.com on Dec 30, 2025, 14:53 UTC