Avoid using runtime finalizers on exit

Docs > Plateforme de sécurité Datadog > Code Security > Static Code Analysis (SAST) > SAST Rules > Avoid using runtime finalizers on exit

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Metadata

ID: kotlin-security/no-finalizers-on-exit

Language: Kotlin

Severity: Error

Category: Security

CWE: 833

Description

This ensures the proper termination of Kotlin programs. It is generally considered unsafe to use the System.runFinalizersOnExit(true) method because it can lead to unpredictable program behavior. This method forces all objects undergoing finalization to be finalized when the JVM exits, which can cause problems if an object is in the middle of a critical operation.

Instead of System.runFinalizersOnExit(true), you can use the Java Runtime API’s addShutdownHook method. This method registers a new virtual-machine shutdown hook, meaning it adds a thread to run when the JVM begins its shutdown sequence. This allows you to handle any cleanup actions yourself, providing a safer and more predictable termination process.

Non-Compliant Code Examples

fun foo() {
  System.runFinalizersOnExit(true)
}

Compliant Code Examples

fun main() {
    Runtime.getRuntime().addShutdownHook(object : Thread() {
        override fun run() {
            handleShutdown()
        }
    })
}