Java Finalization to be Deprecated?

| by Ben Evans Follow 31 Followers on Mar 27, 2017. Estimated reading time: 1 minute |

A recent mail in the OpenJDK mailgroup core-libs-dev has proposed the deprecation of the method Object.finalize().

The deprecation of a method present on Java's Object type, would be a highly unusual step. The finalize() method has been present since Java 1.0, and is widely regarded as a misfeature and a significant piece of legacy cruft in the platform.

An object that overrides finalize() is treated specially by the garbage collector. Usually, an object is immediately destroyed during the collection cycle after the object is no longer in scope. However, finalizable objects are instead moved to a queue, where separate finalization threads will drain the queue and run the finalize() method on each object. Once the finalize() method terminates, the object will at last be ready for garbage collection in the next cycle.

The aim of the mechanism was to provide an equivalent in Java to the C++ RAII pattern, where resources (such as filehandles) are acquired when an object is created and automatically released when the object is destroyed.

However, finalization does not safely implement automatic resource management, as the garbage collector does not run with any time guarantees. This means that there is nothing in the mechanism which ties resource release to the lifetime of the object, and so it is always possible to exhaust resources.

Using finalization is therefore not fit for the main purpose it was originally implemented.

The advice given to developers by Oracle (and Sun) has, for many years, been to avoid finalization in ordinary application code. This deprecation is a first step towards eventual removal, but all it actually does is to introduce a formal compiler warning if the finalization mechanism is used.

The actual removal of the feature does not have any timeline yet, partly because there are some use cases for finalization within the platform that are not tied to management of potentially scarce resources. Consensus has yet to emerge about how to migrate those use cases to alternatives.

Assuming that this deprecation warning does indeed ship as part of Java 9 (as seems likely), then the earliest that removal could occur is Java 10. However, it is unclear that removal would definitely happen in that release, or in any later one.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

pointless by Steven Sagaert

This changes nothing since Sun/Oracle have never ever removed any deprecated method, even the ones that have been deprecated since java 1.1! So it's extremely unlikely that a fundamental one like finalize would ever be removed.

Re: pointless by Ben Evans

Java has always maintained backwards binary compatability. So until the platform was capable of maintaining backwards compatiblity whilst making breaking binary changes (e.g. interface evolution) removal of old, bad methods was not a possibility.

If you read the thread that starts from the link, then you will see that there's quite an in-depth discussion about the possibility of removal. It isn't fully agreed upon, because there are (somewhat edge-case) mechanisms that arguably could use finalization safely, and there is debate about what mechanism they could / should use instead, if finalization was removed.

So, whilst it's not a done deal, there's certainly desire, including from many of the Oracle engineers, to see it actually removed.

-Ben (author)

Clarification from Twitter by Ben Evans

Stuart Marks, one of the Oracle Java engineers clarifies that what is being proposed for Java 9 is deprecation without forRemoval=true. So, the earliest that this method could be removed is Java 11, as Java 10 would have to flip that flag, if the decision was made to remove it.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

3 Discuss

Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you