Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 9
Affects Version/s: 9
Component/s: core-libs
Labels:

Subcomponent:
java.lang
Resolved In Build:
b165

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8178736	10	Roger Riggs	P3	Resolved	Fixed	b05

Finalizers are inherently problematic and their use can lead to performance issues,
deadlocks, hangs, and other problematic behavior.

Furthermore the timing of finalization is unpredictable with no guarantee that a finalizer will be called.
Classes whose instances hold non-heap resources should provide a method
to enable explicit release of those resources, and they should also implement
java.lang.AutoCloseable if appropriate.

The java.lang.ref.Cleaner and java.lang.ref.PhantomReference provide more flexible and
efficient ways to release resources when an object becomes unreachable.

backported by

JDK-8178736 Deprecate Object.finalize

Resolved

duplicates

JDK-6922236 (ref) Object.finalize should include note on alternatives to finalizers and link to the ref package

Closed

relates to

JDK-8184744 Replace finalizer in crypto classes with Cleaner

Resolved

JDK-8178154 Typo in Object.finalize deprecation javadoc

Closed

JDK-8065614 JEP 277: Enhanced Deprecation

Closed

JDK-8190324 ThreadPoolExecutor should not specify a dependency on finalization

Resolved

JDK-8273102 Delete deprecated for removal the empty finalize() in java.desktop module

Resolved

JDK-8229842 ☂ Eliminate use of deprecated finalize method in JavaFX

Resolved

(3 relates to)

There are no Sub-Tasks for this issue.

Assignee:: Roger Riggs

Reporter:: Roger Riggs

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Due:: 2017-03-27

Created:: 2016-09-07 14:23

Updated:: 2021-09-09 21:54

Resolved:: 2017-04-05 07:29

Details

Backports

Description

Attachments

Issue Links

Sub-Tasks

Activity

People

Dates