-
-
Notifications
You must be signed in to change notification settings - Fork 795
Resolve memory usage issues related to Netty 4.2 update #5536
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
Conversation
…ct-connection-velocity-netty4.2
…ct-connection-velocity-netty4.2
...p/bungeecord/src/main/java/org/geysermc/geyser/platform/bungeecord/GeyserBungeeInjector.java
Outdated
Show resolved
Hide resolved
|
Any ETA when it's get merge into main branch? |
|
As soon as enough people report that it's working! So far, we've had no responses. |
Tested that on |
|
Can you provide a geyser dump? |
…-velocity-netty # Conflicts: # gradle/libs.versions.toml
|
@MatinHQ should be resolved, thanks for the report.
|
|
I tested latest commit it's much better but problem still exist I messaged you on discord for geyser dump for privacy reasons I can't share it here |
|
This build does not have the LocalServerChannel error, or any other error on load, that I reported BungeeCord: b1948 |
In order to support io_uring transport after the 4.2 update, we'd need to separately handle 4.1 and 4.2 event loop group creation
bce2866 to
5315749
Compare
Should fix #5467, fix #5468 (the actual bungee/velocity issues reported on there; the issue on geyser-spigot by the original author seems completely unrelated), fix #5482, fix #5510
These builds will also require using the latest BungeeCord & Velocity builds to properly work!
You can download the new builds here:
TODO: