Crash on startup on Debian 11 (SIGSEGV in libdl.so.2)

[syscon3]

Describe the bug

XPipe crashes immediately on startup. The crash occurs consistently on a Debian 11 system and
has been observed with versions 18.1.1 and 18.7. The crash generates a Java HotSpot VM fatal
error log (hs_err_pid*.log).

The crash seems to be a SIGSEGV segmentation fault occurring in native code within
libdl.so.2, related to dynamic library loading by the GraalVM runtime. The trigger for the
crash varies; one log shows it happening during an HttpClient operation, while another shows
it during AWT (graphics) initialization.

To Reproduce

1. Install XPipe on a Debian 11 (bullseye) system.
2. Launch the application.
3. The application fails to start, and a hs_err_pid*.log file is created in the user's home
   directory.

Expected behavior

The XPipe application should start and display the main user interface.

Crash Logs

I have attached the two crash logs generated by the application. These files contain the full
stack traces and system details.

• hs_err_pid255295.log (crashed on version 18.1.1, network-related)
• hs_err_pid14306.log (crashed on version 18.7, graphics-related)

System Information:

• OS: Debian GNU/Linux 11 (bullseye)
• Architecture: x86_64
• XPipe Versions Tested: 18.1.1, 18.7
• Kernel: Linux 5.10.0-35-amd64

Additional context

The issue appears to be a fundamental incompatibility between the GraalVM runtime bundled with
XPipe and the native libraries on Debian 11, specifically concerning the dynamic linker. The
fact that it crashes in dlerror itself is suspicious and might point to a subtle ABI
incompatibility.

hs_err_pid11201.log
hs_err_pid255295.log

[crschnick]

Yeah this showed up a while ago, however I was not able to reproduce it.

Someone else who was affected said that it didn't happen all the time and only on startup of xpipe, so just starting xpipe multiple times until it started up properly without crashing worked.

Can you try whether the same issue occurs with XPipe 19? The JDK was updated from GraalVM 24 to GraalVM 25, maybe they fixed something there.

[syscon3]

Now I run Xpipe only downloading the app and runing this command

CDS_JVM_OPTS="-Dio.xpipe.app.useVirtualThreads=false" /home/xxxx/Apps/xpipe-19.0.2/lib/runtime/bin/xpiped

[crschnick]

If that doesn't crash, that's good to know.

You can also try to run /home/xxxx/Apps/xpipe-19.0.2/bin/xpiped -Dio.xpipe.app.useVirtualThreads=false, that should have the same effect without overriding the variable CDS_JVM_OPTS