It may result in finalizers being called on live objects while other threads are concurrently manipulating those objects, resulting in erratic behavior or deadlock. While this problem could be prevented if the class whose objects are being finalized were coded to "defend against" this call, most programmers do not defend against it. They assume that an object is dead at the time that its finalizer is called.
Further, the call is not "thread-safe" in the sense that it sets a VM-global flag. This forces every class with a finalizer to defend against the finalization of live objects!
[1] https://docs.oracle.com/javase/9/docs/api/java/lang/doc-files/threadPrimitiveDeprecation.html
- blocks
-
JDK-8177680 Umbrella: JDK 11 terminal deprecations
-
- Resolved
-
- csr for
-
JDK-8198250 Remove deprecated Runtime::runFinalizersOnExit and System::runFinalizersOnExit
-
- Closed
-
- relates to
-
-
- Open
-
-
JDK-8288984 Simplification in java.lang.Runtime::exit
-
- Resolved
-
-
JDK-8193035 remove terminally deprecated APIs from java.lang
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Resolved
-
-
-
- Closed
-