Player is able to join, then is kicked out of the game as if the server crashed (1.19.2 - Forge 43.2.3 - modlist included)

[Sushine]

A few players of mine have been experiencing the issue of being able to join my server for maybe 30 seconds, before they seemingly freeze to everyone else, but are in actuality kicked out of the server as if it had crashed. Absolutely no clue what can cause this. It doesn't look like anything happens when I have the spark profiler running, but something is definitely going on. When they try to join and get disconnected the server log says "handleDisconnection() called twice". If any more info is needed, please feel free to ask, we can easily recreate this. 

Modlist

[warjort]

We need a link to the user's logs/debug.log so we can see the error they are getting.

[Sushine]

10 minutes ago, warjort said:

We need a link to the user's logs/debug.log so we can see the error they are getting.

He gave me two logs, a debug.log and a debug-1.log. Here's a link to download both, couldn't get them into pastebin. https://drive.google.com/drive/folders/1pD8Uee6XrL3MpTl5SJUC0neLiSw1y83Z?usp=sharing

[warjort]

It might be related to these messages? Showing a mod mismatch between the client and server?

Quote

[13Jan2023 21:01:26.703] [Netty Client IO #6/DEBUG] [net.minecraftforge.client.ForgeHooksClient/CLIENTHOOKS]: Received FML ping data from server at 135.148.64.153: FMLNETVER=3, mod list is compatible : false, channel list is compatible: true, extra server mods: {smoothchunk=1.19.1-2.0, saturn=0.0.1, pluto=0.0.7, clumps=9.0.0+14, amplified_nether=0.0NONE, nullscape=0.0NONE}
[13Jan2023 21:01:26.703] [Netty Client IO #6/INFO] [net.minecraftforge.client.ForgeHooksClient/CLIENTHOOKS]: Server has additional mods that may be needed on the client: [email protected], [email protected], [email protected], [email protected]+14, [email protected], [email protected]
[13Jan2023 21:01:26.703] [Netty Client IO #6/INFO] [net.minecraftforge.client.ForgeHooksClient/CLIENTHOOKS]: Client has mods that are missing on server: [konkrete, smoothboot, justzoom]
 

 

Around the disconnect, there are some earlier errors related to rendering which suggests one of the mods is doing something unsupported by the graphics driver?

Quote

[13Jan2023 21:01:44.851] [Render thread/ERROR] [com.mojang.blaze3d.platform.Window/]: ########## GL ERROR ##########
[13Jan2023 21:01:44.851] [Render thread/ERROR] [com.mojang.blaze3d.platform.Window/]: @ Pre render
[13Jan2023 21:01:44.851] [Render thread/ERROR] [com.mojang.blaze3d.platform.Window/]: 65539: Invalid key 3

 

There are some "warnings" from create/flywheel just before they are kicked.

The last thing in the log is from the xaero's map mod, but these are status messages rather than errors/warnings.

Quote

[13Jan2023 21:01:55.663] [Render thread/DEBUG] [com.jozufozu.flywheel.backend.Backend/]: No active uniform 'uTime' exists in program 'flywheel:oriented'. Could be unused.
[13Jan2023 21:01:55.663] [Render thread/DEBUG] [com.jozufozu.flywheel.backend.Backend/]: No active uniform 'uWindowSize' exists in program 'flywheel:oriented'. Could be unused.
[13Jan2023 21:01:55.983] [Render thread/DEBUG] [mixin/]: Mixing ai.pathing.FlyNodeEvaluatorMixin from canary.mixins.json into net.minecraft.world.level.pathfinder.FlyNodeEvaluator
[13Jan2023 21:02:25.724] [Render thread/INFO] [xaero.common.MinimapLogs/]: Minimap session finalized.
[13Jan2023 21:02:25.724] [Render thread/INFO] [xaero.map.WorldMap/]: Finalizing world map session...
[13Jan2023 21:02:25.765] [Thread-8/INFO] [xaero.map.WorldMap/]: World map cleaned normally!
[13Jan2023 21:02:26.324] [Render thread/INFO] [xaero.map.WorldMap/]: World map session finalized.
[13Jan2023 21:02:26.324] [Render thread/INFO] [mezz.jei.forge.startup.StartEventObserver/]: JEI StartEventObserver received class net.minecraftforge.client.event.ClientPlayerNetworkEvent$LoggingOut

 

Maybe try turning off create's special flywheel rendering?

https://forums.minecraftforge.net/topic/119518-exit-code-1073740940/#comment-524102

 

Also ask the user if they get this problem if they play with the same mods in single player.

[Sushine]

41 minutes ago, warjort said:

It might be related to these messages? Showing a mod mismatch between the client and server?

 

Around the disconnect, there are some earlier errors related to rendering which suggests one of the mods is doing something unsupported by the graphics driver?

 

There are some "warnings" from create/flywheel just before they are kicked.

The last thing in the log is from the xaero's map mod, but these are status messages rather than errors/warnings.

 

Maybe try turning off create's special flywheel rendering?

https://forums.minecraftforge.net/topic/119518-exit-code-1073740940/#comment-524102

 

Also ask the user if they get this problem if they play with the same mods in single player.

Okay, asked them to update their graphics drivers, didnt work. Told them to change the thing in flywheel, didn't work. Finally, he says that he's not having the issue in a single player world.

[warjort]

If it's not flywheel then you should ask them to try removing any client side graphics mods they have like rubidium or optifine.

 

Also, ssk them to add the following system property to their java (jvm) arguments

Quote

-Dforge.logging.mojang.level=debug

this will let us see what is happening at the network level and what error (if any) they are getting there.

 

Otherwise, without an explicit crash error, probably the only way you are going to find the problem is by experimenting with removing mods using a test server.

So you can locate which mod is causing the problem.