Minecraft Version

1.21.1 (LTS)

Mod Loader

NeoForge

Describe the Issue

Dedicated server crashes every few hours and every time the crash log has watchdog blaming Waystones for ticking.

Modlist: https://pastebin.com/a7srbs5f

This is my client's modlist. The server's modlist does not include client-only mods like Sodium. It does include Jade and JEI for server-side info.

Hosted using PebbleHost.

Logs

The lists correspond to each other.

Crash reports:

1. https://mclo.gs/23uhdta
2. https://mclo.gs/4Ivr7Al
3. https://mclo.gs/g5Y25QV
4. https://mclo.gs/15cNxJj
5. https://mclo.gs/COqBkBu
6. https://mclo.gs/78kjSIo
7. https://mclo.gs/ASueK1S

Logs:

1. https://mclo.gs/nB6xKDp
2. https://mclo.gs/2KFbPKu
3. https://mclo.gs/fFi4X2T
4. https://mclo.gs/uoPn0Yp
5. https://mclo.gs/wHvgKwq
6. https://mclo.gs/JpH2r6I
7. https://mclo.gs/SpLNSho

Looking into it, turns out I was wrong and it does not actually load every waystone chunk when accessing the menu. Chunks are only loaded when an actual teleport is about to occur.

Not sure what caused the latest crash in your case without the corresponding logs.

Waystones in those logs is merely attempting to load a chunk from the main thread after someone tried to teleport.

Something else, likely a world generation or performance mod, is causing a deadlock freezing the server.

Waystones in those logs is merely attempting to load a chunk from the main thread after someone tried to teleport.

Something else, likely a world generation or performance mod, is causing a deadlock freezing the server.

Thank you for the reply!

This doesn't happen when traveling or when using /tp command, and it also happens when using Waystones while the chunk is already loaded by someone else. I'll look into it though...

It seems weird that the server crashes in this way when opening the Waystones screen.
It was just me and another player on the server, standing in place. The other player opened a Waystone and the server crashed.

Does the Waystone GUI try to load every single Waystone chunk when accessed?

Good catch, it does, and it really shouldn't.

I'm not sure whether fixing that will do anything about the deadlocks (if there even are any, or maybe you just have a huge amount of waystones), but it sure can't hurt.

Good catch, it does, and it really shouldn't.

I'm not sure whether fixing that will do anything about the deadlocks (if there even are any, or maybe you just have a huge amount of waystones), but it sure can't hurt.

Thanks again for the reply!

And yeah, the deadlocks are definitely a me problem lol, but if I can encounter them organically by entering the problematic chunk or something, I could pinpoint the problem better ^^

Looking into it, turns out I was wrong and it does not actually load every waystone chunk when accessing the menu. Chunks are only loaded when an actual teleport is about to occur.

Not sure what caused the latest crash in your case without the corresponding logs.

thank you for looking into it!

is there a way to find out exactly which chunk the waystone tried to load when the crash occurred?

and well, the crash/logs are pretty much all the same, if you'd like to see. here are some:
crash | log
crash | log
crash | log

is there a way to find out exactly which chunk the waystone tried to load when the crash occurred?

It would be the chunk that you're teleporting to.

The crashlogs show a waystone being selected which is why it tries to load the chunk.