florekk925 opened a new issue, #5212:
URL: https://github.com/apache/hop/issues/5212
### Apache Hop version?
apache/hop:latest
### Java version?
apache/hop:latest
### Operating system
Docker
### What happened?
After upgrading to version `2.13` (latest), my container crashes with a
segmentation fault (SIGSEGV) during execution. This issue did **not** occur
with version `2.12`, which worked without problems.
The fatal error is triggered while using pipeline to write data from Google
BigQuery to a PostgreSQL database.
Last line from pipline log before crash:
2025/04/23 07:39:26 - xxxxxxxxxxx.0 - Connected to database [psql]
(commit=1000)
### Error output
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00000000000204b6, pid=292, tid=458
JRE version: OpenJDK Runtime Environment (17.0.15+6) (build
17.0.15+6-alpine-r0)
Java VM: OpenJDK 64-Bit Server VM (17.0.15+6-alpine-r0, mixed mode,
sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
Problematic frame:
C
[libio_grpc_netty_shaded_netty_tcnative_linux_x86_6412750308596017923277.so+0x2a154]
netty_internal_tcnative_SSLContext_JNI_OnLoad+0x9c4
Core dump will be written. Default location: Core dumps may be processed
with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to
/opt/hop/core.292)
An error report file with more information is saved as:
/opt/hop/hs_err_pid292.log
If you would like to submit a bug report, please visit:
https://gitlab.alpinelinux.org/alpine/aports/issues
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
/opt/hop/hop-run.sh: line 94: 292 Aborted (core dumped)
"${_HOP_JAVA}" ${HOP_OPTIONS} -Djava.library.path="${LIBPATH}" -classpath
"${CLASSPATH}" org.apache.hop.run.HopRun "$@"
### Issue Priority
Priority: 3
### Issue Component
Component: Containers
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
