Upgrade to a newer Java version

Oct 13, 2025 by orovajewels.com 38 views

Netty: The Crash Happened Outside the Java Virtual Machine in Native Code

In this article, we will explore a common issue encountered when using Netty with a specific Java version and Docker image. The problem arises when the application crashes outside the Java Virtual Machine (JVM) in native code, resulting in a SIGSEGV error. We will delve into the details of the issue, provide possible solutions, and offer recommendations for resolving this bug.

The issue at hand is related to the use of the eclipse-temurin:22-jdk-alpine image for the Docker image. This image is based on Alpine Linux, which is a lightweight Linux distribution. The application was previously using spring boot 3.3.0 without any issues. However, after upgrading to spring boot 3.4.3, the application started crashing with a Netty-related error.

The error message is as follows:

web-server  | #
web-server  | # A fatal error has been detected by the Java Runtime Environment:
web-server  | #
web-server  | #  SIGSEGV (0xb) at pc=0x00000000000204b6, pid=1, tid=7
web-server  | #
web-server  | # JRE version: OpenJDK Runtime Environment Temurin-23.0.2+7 (23.0.2+7) (build 23.0.2+7)
web-server  | # Java VM: OpenJDK 64-Bit Server VM Temurin-23.0.2+7 (23.0.2+7, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
web-server  | # Problematic frame:
web-server  | # C  [libio_grpc_netty_shaded_netty_tcnative_linux_x86_644120885934021866491.so+0x2a154]  netty_internal_tcnative_SSLContext_JNI_OnLoad+0x9c4
web-server  | #
web-server  | # Core dump will be written. Default location: Core dumps may be processed with "/wsl-capture-crash %t %E %p %s" (or dumping to //core.1)
web-server  | #
web-server  | # An error report file with more information is saved as:
web-server  | # //hs_err_pid1.log
web-server  | [16.171s][warning][os] Loading hsdis library failed
web-server  | #
web-server  | # If you would like to submit a bug report, please visit:
web-server  | #   https://github.com/adoptium/adoptium-support/issues
web-server  | # The crash happened outside the Java Virtual Machine in native code.
web-server  | # See problematic frame for where to report the bug.
web-server  | #

The error message indicates that the crash occurred outside the JVM in native code. The problematic frame is related to the libio_grpc_netty_shaded_netty_tcnative_linux_x86_644120885934021866491.so library, which is part of the Netty library. This suggests that the issue is related to the interaction between Netty and the native code.

Based on the analysis, the following possible solutions can be considered:

Upgrade to a newer Java version: Try upgrading to a newer Java version, such as eclipse-temurin:23-jdk-alpine, to see if the issue is resolved.
Use a different Docker image: Try using a different Docker image, such as eclipse-temurin:22-jdk, which is based on Debian instead of Alpine Linux.
Disable native code: Try disabling native code in Netty to see if the issue is resolved.
Submit a bug report: Submit a bug report to the Adoptium support team to report the issue and seek further assistance.

Based on the analysis and possible solutions, the following recommendations can be made:

Use a different Docker image: Consider using a different Docker image, such as eclipse-temurin:22-jdk, which is based on Debian instead of Alpine Linux.
Upgrade to a newer Java version: Consider upgrading to a newer Java version, such as eclipse-temurin:23-jdk-alpine, to see if the issue is resolved.
Disable native code: Consider disabling native code in Netty to see if the issue is resolved.
Submit a bug report: Consider submitting a bug report to the Adoptium support team to report the issue and seek further assistance.

In conclusion, the issue encountered with Netty and the eclipse-temurin:22-jdk-alpine image is likely related to the interaction between Netty and the native code. The possible solutions and recommendations provided can help resolve the issue. However, further investigation and testing may be required to determine the root cause of the problem.
Netty: The Crash Happened Outside the Java Virtual Machine in Native Code - Q&A

In our previous article, we explored a common issue encountered when using Netty with a specific Java version and Docker image. The problem arises when the application crashes outside the Java Virtual Machine (JVM) in native code, resulting in a SIGSEGV error. In this article, we will provide a Q&A section to address some of the frequently asked questions related to this issue.

A: The crash is likely caused by the interaction between Netty and the native code. The problematic frame is related to the libio_grpc_netty_shaded_netty_tcnative_linux_x86_644120885934021866491.so library, which is part of the Netty library.

A: There are several possible solutions to resolve the issue:

Upgrade to a newer Java version: Try upgrading to a newer Java version, such as eclipse-temurin:23-jdk-alpine, to see if the issue is resolved.
Use a different Docker image: Try using a different Docker image, such as eclipse-temurin:22-jdk, which is based on Debian instead of Alpine Linux.
Disable native code: Try disabling native code in Netty to see if the issue is resolved.
Submit a bug report: Submit a bug report to the Adoptium support team to report the issue and seek further assistance.

A: Alpine Linux is a lightweight Linux distribution that is designed to be small and efficient. Debian, on the other hand, is a more traditional Linux distribution that is widely used and well-supported. The difference in Linux distribution may be contributing to the issue.

A: Yes, you can try using a different version of Netty to see if the issue is resolved. However, be aware that using a different version of Netty may introduce new issues or dependencies.

A: To disable native code in Netty, you can set the following system property:

-Dio.netty.useNativeTransport=false

A: The best way to troubleshoot the issue is to:

Enable debug logging: Enable debug logging in Netty to get more detailed information about the issue.
Use a debugger: Use a debugger to step through the code and identify the source of the issue.
Submit a bug report: Submit a bug report to the Adoptium support team to report the issue and seek further assistance.

In conclusion, the issue encountered with Netty and the eclipse-temurin:22-jdk-alpine image is likely related to the interaction between Netty and the native code. The Q&A section provided in this article should help address some of the frequently asked questions related to this issue. However, further investigation and testing may be required to determine the root cause of the problem.