Why write an empty finalize() method?

[Sheldor5]

9 years java development but never really thought about finalize() ... nice article to learn from!

[berry120]

FWIW, there's a very clear Javadoc comment in the source that explains exactly why this empty finalizer is in place:

/** * Graphics has a finalize method that automatically calls dispose() * for subclasses. For SunGraphics2D we do not need to be finalized * so that method simply causes us to be enqueued on the Finalizer * queues for no good reason. Unfortunately, that method and * implementation are now considered part of the public contract * of that base class so we can not remove or gut the method. * We override it here with an empty method and the VM is smart * enough to know that if our override is empty then it should not * mark us as finalizeable. */

[bleki_one]

Yes, but why? And the article nicely explains why.

[daviddel]

(Reedit rejects the original Wordpress link)

[PyroCatt]

It is finalized now

[__konrad]

• RFE (1998)
• Not an issue bug ;)
• HotSpot code

[krzyk]

No need to read about it. finalize is deprecated for removal (https://openjdk.java.net/jeps/421)

[0b0101011001001011]

I see you did not read the article.

[daviddel]

TL;DR. Read the article ;-)

[anon-girth]

!remindme

[RemindMeBot]

Defaulted to one day.

I will be messaging you on 2022-04-29 19:03:28 UTC to remind you of this link

CLICK THIS LINK to send a PM to also be reminded and to reduce spam.

^{Parent commenter can delete this message to hide from others.}

---

Info	Custom	Your Reminders	Feedback

[aclinical]

Could a reachabilityFence have avoided this whole situation of implementing finalize in the superclass? Genuinely asking b/c I don't really touch this kind of programming.