建议 / 问题反馈

THIS BUG HAS ALREADY BEEN POSTED! https://labymod.net/en/idea/12035
This entry is just go a little bit more detail as I tried multiple different solutions.

So basically, when trying to join a server in 1.8.9, it doesnt work and gives this message:

Internal Exception: java.lang.RuntimeException: Unable to access address of buffer

Here is a screenshot of it:

This, apparently is caused due to running 1.8.9 on java 17. When forcefully running 1.8.9 on java 8, it doesnt launch at all.

To reproduce this issue:

1. Use linux*
2. Install Labymod 4, 1.8.9 and launch it
3. connect to server

Expected result:
Join server properly

Actual result:
unable to join server

*Linux distros that have this issue:
Fedora-based, Debian-based. This probably means most if not all of the linux distros have this issue.
I am not sure about Arch based linux distros but I will try launching in Arch after I post this and post the results.

Java vendors that have this issue:
GraalVM EE, openjdk-based java vendors, the java shipped with linux distros by default. All of these are Java 17. When Launching in Java 17, I am unable to join servers. I am able to play single player.
When bypassing java compatibility checks in Multimc (prismlauncher) and forcefully launching LabyMod 4, causes it to not launch and exits with code 199 (Log: https://mclo.gs/SqcP5pA).

In Java 17, after launch, the logs are spammed with error messages, infinitely (https://mclo.gs/fXjikmD)

I am not sure if this is related but this also warns this in the logs:
INFO: Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.

Operating System: Linux
LabyMod Version: 4.0.0+821 snapshot/4b60acc
Minecraft Version: 1.8.9
Installed Addons: none