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
When encountering an error while predicting with xgboost on Linux arm64, how should it be handled? The deployment environment is Linux aarch64, DJL xgboost version is 0.26.0,and the JDK version is 1.8.0_312. Interestingly, when switching to JDK 11.0.11, the error disappears and it can run normally.
The specific error is "# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000007fa4b04a4c, pid=545530, tid=0x0000007fbc4921e0
#
# JRE version: OpenJDK Runtime Environment (8.0_312-b07) (build 1.8.0_312-8u312-b07-0kylin1~20.04-b07)
# Java VM: OpenJDK 64-Bit Server VM (25.312-b07 mixed mode linux-aarch64 compressed oops)
# Problematic frame:
# C [libxgboost4j7032141238325234706.so+0x205a4c] std::filesystem::path::~path()+0xc
#
# Core dump written. Default location: /home/xgboostJava/core or core.545530
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.".
I kindly request assistance in resolving the error message. Could you please provide guidance on how to address this issue?
The text was updated successfully, but these errors were encountered:
Thank you for your answer. As we further investigate, we found that the issue is with the JDK that comes with the Linux Kylin system. There is no such issue with the JDK 1.8 downloaded from the official website.
Description
When encountering an error while predicting with xgboost on Linux arm64, how should it be handled? The deployment environment is Linux aarch64, DJL xgboost version is 0.26.0,and the JDK version is 1.8.0_312. Interestingly, when switching to JDK 11.0.11, the error disappears and it can run normally.
I kindly request assistance in resolving the error message. Could you please provide guidance on how to address this issue?
The text was updated successfully, but these errors were encountered: