-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on join #17
Comments
This seems to be caused by netty, a temporary fix is to disable "use-native-transport" in server.properties |
Can confirm turning off use native transport does fix it. Since you seem to know, what does use native transport actually even do? |
generate less garbage, and generally improve performance when compared to the NIO based transport. |
_wut, that's not true, if that was the case we would all disable it. What native transport does is use the java based networking, while Netty NIO uses special system level calls that can optimize packet sending. as well as bytebuf to use byte arrays on the heap instead off on the stack, which allows netty to produce less garbage, thus less GC time. It breaks on java 17 because the current version of netty we use in BurritoSpigot doesn't support that java 17_ |
Netty says that 😔 i got lied my whole life |
Let me read more about this |
crash-2022-01-02_21.54.12-server.txt |
Crashing could happen when someone joined. Plugins can see in these reports. |
It seems like server crashes randomly when people join. |
When I join the server the following error spams console and I am unable to connect from the server.
I am using debian and jdk 17. The plugins used are listed in the crash log (a /pl query was issued). The deluxehub version has been motified to accept unknown 1.8 server versions and has worked without issue on TacoSpigot and other 1.8 spigots I have used before.
crash.txt
The text was updated successfully, but these errors were encountered: