Server crash with Quantum Rings? (Too many chained neighbor updates)
SHOEGAZEssb opened this issue · 7 comments
Describe the bug
Today when I tried to login to my server (we're running a custom modpack) I couldnt get on. Checked the server logs and saw it crashing directly after startup.
After a few retries the server started without crashing.
How to reproduce the bug
Server crash on startup
Expected behavior
No server crash on startup
Additional details
The weird thing is, that it worked fine yesterday evening when I logged off, and the server was running the full time.
We're using Forge 47.2.1 and AE2 15.0.15.
Which minecraft version are you using?
1.20
On which mod loaders does it happen?
Forge
Crash log
Running a server with forge and over night the server had the same issue. Do you have a fix ?
Running a server with forge and over night the server had the same issue. Do you have a fix ?
I did update to Forge 47.2.17, since then this didnt happen again
Seeing this as well with Applied Energistics 2, version 15.0.15, as part of All The Mods 9. Server starts successfully, but as soon as someone joins it hangs with the same console log entry about too many chained neighbor updates.
Updating to Forge 47.1.17 did not fix the issue for me.
Additional information from a user: the issue started after someone built a quantum ring and spatial anchor in the nether.
Additionally, I have attempted to work around the issue by setting max-chained-neighbor-updates in server.properties to -1 in order to disable that check. This did not work. Instead, on a login attempt, server memory climbs until it hits the memory limit for the server, at which point the server hangs.
This issue also happens on singleplayer. I loaded the server map on my local machine, and Minecraft immediately maxed out memory usage and hung.
also having a similar issue in singleplayer on NeoForged, trying the latest Forge version produces the same crash
crash-2024-01-03_12.51.55-server.txt
