Application crashes with an image base liberica-openjre-alpine in s3Transfer copy operation

[cenkakin]

Describe the bug

Since the release of version 0.24.0 0.23.0, our application has been crashing during the execution of s3Transfer copy operation.

It's running on JDK 17 and we use bellsoft/liberica-openjre-alpine:17.0.8 as a base image.

The code has been tested and confirmed to run smoothly on amazoncorretto:17.0.8 and may also work on other base images.

Expected Behavior

It doesn't crash in liberica images.

Current Behavior

The application crashes. Here are the logs:

[error occurred during error reporting ((null)), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing fatal error message), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing type of error), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing exception/signal name), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing current thread and pid), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing error message), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing Java version string), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing problematic frame), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing core file information), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing jfr information), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing bug submit message), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing summary), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing VM option summary), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing summary machine and OS info), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing date and time), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing thread), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing current thread), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing current compile task), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing stack bounds), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing native stack), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing Java stack), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing target Java thread stack), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing siginfo), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (CDS archive access warning), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing register info), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing registers, top of stack, instructions near pc), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (inspecting top of stack), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing code blob if possible), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing VM operation), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[error occurred during error reporting (printing process), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]


[error occurred during error reporting (printing user info), id 0xb, SIGSEGV (0xb) at pc=0x00007ff917c0dcf4]

[Too many errors, abort]
[Too many errors, abort]

Reproduction Steps

I have created a sample project along with a guide on how to run it: https://github.com/cenkakin/aws-crt-liberica-problem

Please let me know if you need further assistance.

Possible Solution

No response

Additional Information/Context

No response

aws-crt-java version used

0.24.0 0.23.0

Java version used

17

Operating System and version

FROM bellsoft/liberica-openjre-alpine:17.0.8

[waahm7]

@cenkakin Thank you for creating the issue. Can you please confirm if this issue only started happening on v0.24.0 and worked fine on v0.23.2? We are looking into this issue, in the meanwhile, you can try using the musl based bellsoft/liberica-openjre-alpine-musl:17.0.8 image as a workaround.

[cenkakin]

Hi @waahm7! Thanks for the quick reply. I made a mistake by saying that it was introduced at v0.24.0. On further investigation, I realized that the version we used was actually 0.22.2, not 0.23.2. Based on my testing, it appears that the bug is present in [v0.23.0] (cenkakin/aws-crt-liberica-problem@bb2db7d), while the previous version, v0.22.5, is functioning properly (cenkakin/aws-crt-liberica-problem@main...ver0.22.5).
Sorry for the confusion, I'm updating the bug description as well.

in the meanwhile, you can try using the musl based bellsoft/liberica-openjre-alpine-musl:17.0.8 image as a workaround.

We have decided to roll back the update temporarily. We will wait for you to fix the issue. Thank you for your suggestion.

[graebm]

Ok, try the latest release 0.25.0.
It should automatically detect that Java is using glibc (despite being on Alpine which uses musl for most things).

But also you can now manually set the -Daws.crt.libc=glibc system property to force glibc or musl, and unblock yourself if we need to improve the detection.

Please let us know if the new automatic detection works or not.

[cenkakin]

Yes, it's working smoothly! Thank you for the fast turnaround, we appreciate it.