Request: give meaningful error message when attempting to use on heap buffers when creating data buffers · Issue #10214 · deeplearning4j/deeplearning4j · GitHub
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
{{ message }}
Repository navigation
Request: give meaningful error message when attempting to use on heap buffers when creating data buffers #10214
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x000000018b2503f4, pid=83713, tid=3843
#
# JRE version: Java(TM) SE Runtime Environment Oracle GraalVM 21.0.2+13.1 (21.0.2+13) (build 21.0.2+13-LTS-jvmci-23.1-b30)
# Java VM: Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 21.0.2+13.1 (21.0.2+13-LTS-jvmci-23.1-b30, mixed mode, sharing, tiered, jvmci, jvmci compiler, compressed oops, compressed class ptrs, g1 gc, bsd-aarch64)
# Problematic frame:
# C [libsystem_platform.dylib+0x33f4] _platform_memmove+0x1a4
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/xxx/hs_err_pid83713.log
#
# If you would like to submit a bug report, please visit:
# https://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.
#
Process finished with exit code 134 (interrupted by signal 6:SIGABRT)
i am not saying non-direct ByteBuffer needs to be supported, but it would have saved me a lot of time if it just gave a useful error message instead of crashing the JVM
changed the title [-]using a non-direct ByteBuffer crashes the JVM[/-][+]Request: give meaningful error message when attempting to use on heap buffers when creating data buffers[/+]on Jun 24, 2025
Activity
agibsonccc commentedon Jun 24, 2025
@sdyura I'm not fixing this. Use Bytebuffer.allocateDirect(..) it works that way for a reason. All nd4j data is off heap.
sdyura commentedon Jun 24, 2025
i am not saying non-direct ByteBuffer needs to be supported, but it would have saved me a lot of time if it just gave a useful error message instead of crashing the JVM
agibsonccc commentedon Jun 24, 2025
@sdyura Sorry about that. Let me reword the issue and I'll ensure that's in there.
[-]using a non-direct ByteBuffer crashes the JVM[/-][+]Request: give meaningful error message when attempting to use on heap buffers when creating data buffers[/+]