我刚刚扫描的所有答案的缺失形式是终结器更安全的替代品。关于使用try-with-resources和避免终结器，所有其他答案都是正确的，因为它们不可靠，现在已弃用……

但是他们没有提到清洁工。Java 9中添加了清洁器，以一种比终结器更好的方式显式地处理清理工作。

https://docs.oracle.com/javase/9/docs/api/java/lang/ref/Cleaner.html

随着Java 1.7的发布，现在有了使用try-with-resources块的额外选项。例如,

public class Closeable implements AutoCloseable {
    @Override
    public void close() {
        System.out.println("closing..."); 
    }
    public static void main(String[] args) {
        try (Closeable c = new Closeable()) {
            System.out.println("trying..."); 
            throw new Exception("throwing..."); 
        }
        catch (Exception e) {
            System.out.println("catching..."); 
        }
        finally {
            System.out.println("finalizing..."); 
        } 
    }
}

如果执行这个类，则在try块剩余时，在catch块和finally块执行之前，将执行c.close()。与finalize()方法不同，close()保证被执行。但是，不需要在finally子句中显式地执行它。

我同意大部分答案。

你不应该完全依赖finalize或ShutdownHook

完成

The JVM does not guarantee when this finalize() method will be invoked. finalize() gets called only once by GC thread. If an object revives itself from finalizing method, then finalize will not be called again. In your application, you may have some live objects, on which garbage collection is never invoked. Any Exception that is thrown by the finalizing method is ignored by the GC thread System.runFinalization(true) and Runtime.getRuntime().runFinalization(true) methods increase the probability of invoking finalize() method but now these two methods have been deprecated. These methods are very dangerous due to lack of thread safety and possible deadlock creation.

shutdownHooks

public void addShutdownHook(Thread hook)

注册一个新的虚拟机关闭钩子。

Java虚拟机在响应两种事件时关闭:

The program exits normally, when the last non-daemon thread exits or when the exit (equivalently, System.exit) method is invoked, or The virtual machine is terminated in response to a user interrupt, such as typing ^C, or a system-wide event, such as user logoff or system shutdown. A shutdown hook is simply an initialized but non-started thread. When the virtual machine begins its shutdown sequence it will start all registered shutdown hooks in some unspecified order and let them run concurrently. When all the hooks have finished it will then run all uninvoked finalizers if finalization-on-exit has been enabled. Finally, the virtual machine will halt. Note that daemon threads will continue to run during the shutdown sequence, as will non-daemon threads if the shutdown was initiated by invoking the exit method. Shutdown hooks should also finish their work quickly. When a program invokes exit the expectation is that the virtual machine will promptly shut down and exit. But even Oracle documentation quoted that

在极少数情况下，虚拟机可能会中止，即停止运行而不完全关闭

这发生在虚拟机从外部终止时，例如在Unix上使用SIGKILL信号或在Microsoft Windows上使用TerminateProcess调用。如果本机方法出错，虚拟机也可能中止，例如破坏内部数据结构或试图访问不存在的内存。如果虚拟机中止，则不能保证是否会运行任何shutdown钩子。

结论:合理使用try{} catch{} finally{}块，释放finally(}块中的关键资源。在finally{}块中释放资源时，捕获Exception和Throwable。

也许你可以试试……Finally块来最终确定您正在使用对象的控制流中的对象。当然，它不会自动发生，但在c++中破坏也不会发生。你经常在finally块中看到资源的关闭。

我过去主要处理c++，这也是我寻找析构函数的原因。我现在经常使用JAVA。我所做的，可能对每个人来说都不是最好的，但我实现了我自己的析构函数通过将所有值重置为0或通过函数的默认值。

例子:

public myDestructor() {

variableA = 0; //INT
variableB = 0.0; //DOUBLE & FLOAT
variableC = "NO NAME ENTERED"; //TEXT & STRING
variableD = false; //BOOL

}

理想情况下，这并不适用于所有情况，但在有全局变量的情况下，只要你没有大量的全局变量，它就可以工作。

我知道我不是最好的Java程序员，但它似乎对我有用。

Java没有任何析构函数。在Java中，它背后的主要原因是垃圾收集器总是被动地在后台工作，所有对象都在堆内存中创建，这是GC工作的地方。在c++中，我们必须显式调用delete函数，因为没有垃圾收集器之类的东西。