You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed SIGSEGV fault caused by DJL. This was causing service availability issues since my containers would shut down with this fault. I know that this caused by DJL since after i pushed a revert of the upgrade to production those errors stopped and haven't had an issue with availability since.
With DJL 0.25:
With DJL 0.23 (Revert):
The SIGSEGV looks like
13 Jan 2024 22:28:29,985 �[36m[DEBUG]�[m d92a7fa4-4deb-4471-87f6-b6462710daa3 82a4fa21-065e-4947-97e7-902208c65bf3 (MainExecutorService-17) com.amazonaws.request: Received successful response: 200, AWS Request ID: 4E29OFAT5PFI5E3ROQEPPKS27FVV4KQNSO5AEMVJF66Q9ASUAAJG
13 Jan 2024 22:28:29,985 �[36m[DEBUG]�[m d92a7fa4-4deb-4471-87f6-b6462710daa3 82a4fa21-065e-4947-97e7-902208c65bf3 (MainExecutorService-17) com.amazonaws.requestId: x-amzn-RequestId: 4E29OFAT5PFI5E3ROQEPPKS27FVV4KQNSO5AEMVJF66Q9ASUAAJG
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f2d4952b35d, pid=1, tid=1267
#
# JRE version: OpenJDK Runtime Environment 1.0.1516.0 (17.0.9+13) (build 17.0.9+13-LTS)
# Java VM: OpenJDK 64-Bit Server VM 1.0.1516.0 (17.0.9+13-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
There isn't anything after that in the logs.
The text was updated successfully, but these errors were encountered:
Original issue: dmlc/xgboost#9950
I've noticed
SIGSEGV
fault caused by DJL. This was causing service availability issues since my containers would shut down with this fault. I know that this caused by DJL since after i pushed a revert of the upgrade to production those errors stopped and haven't had an issue with availability since.With DJL 0.25:
With DJL 0.23 (Revert):
The SIGSEGV looks like
There isn't anything after that in the logs.
The text was updated successfully, but these errors were encountered: