On Sat, 13 Sep 2025 07:10:42 GMT, Jaikiran Pai <[email protected]> wrote:
> Can I please get a review of this change which addresses the issue noted in > https://bugs.openjdk.org/browse/JDK-8367597? > > As noted in that issue, on certain occasions, during shutdown of the JVM, the > logging in `Runtime.exit()` generates a `NullPointerException`. The issue is > due to the JVM not being fully initialized when (concurrently) the signal > handler thread calls the `Runtime.exit()` code which then attempts to log a > message. > > The commit in this PR skips the logging from `Runtime.exit()` if the JVM > isn't fully initialized at that point in time. I've manually verified that > this change indeed addresses the issue by running the same tests on the hosts > where this was previously failing. No new regressions tests have been > introduced given the nature of the issue. > > tier1 testing with this change completed without any related issues and > additional tier testing is currently in progress. This pull request has now been integrated. Changeset: 0bc37059 Author: Jaikiran Pai <[email protected]> URL: https://git.openjdk.org/jdk/commit/0bc3705948b1bb8f327dc48c4dbd85d22d66f036 Stats: 5 lines in 1 file changed: 2 ins; 0 del; 3 mod 8367597: Runtime.exit logging failed: Cannot invoke "java.lang.Module.getClassLoader()" because "m" is null Reviewed-by: alanb, rriggs ------------- PR: https://git.openjdk.org/jdk/pull/27270
