david evans

what do u mean software package? like windows 10?

i did post a link to the world save LOL. how did u miss it? not enough information. i thought it was very detailed.

im pretty sure once a world gets to certain size this bug becomes much more noticable. at start it would happen maybe 1/10 times now its every time i enter nether. sometimes when i join it locks too

even right now second i enter the nether server deadlocks and kicks me. also im only one on the local server.

same issue also happens when a buddy would join server and server would deadlock also.

this happens on anything, vanilla-spigot-forge (mods or mods)

Hardware:
Ryzan 2700x with 32 gigs of 3200 ddr4 ram running server on a 3g/bs M2 samsung evo 970 - nothing else installed on HDD - allocted 16 gigs of ram for server.

it happens with large pregen worlds - heres the download link
http://www.mediafire.com/file/ci93do7wrwh51ev/Earth.zip/file

simple earth map ratio of 1:2000

and yes i have used forceupgrade and erase cache. the issue happens more u play the world. esp when u travel to and from nether.
quick way to see this happen is die and respawn few times.

again its a deadlock not a crash so no errors will be shown. ive dealt with looping deadlocks coding java servers for other games. thats how i found this. something is looping with client-server connections.
max-tick-time=1 < deadlocks

max-tick-time=60000 throws a watchdog crash for no reaosn

also i am using forge modded version with same bug but whats strange is that mod events over time still work fine even tho server is deadlocked state.

UPDATE
so after doing some testing i found that server cannot sync with player data from client for some reason which leads to a massive deadlock when a player joins/dies-respawns/changes dim, this is in 1.15.1

also added comment, the deadlock will not show ANY error/logs even when using /debug commands. the bug happens when loading/unloading chunks rapidly AKA going from overworld -> nether -> overworld. the deadlock means theres an infinite looping code running that cannot be broke. from what i heard is that every chunk has its own block ids, this feature is whats causing the deadlocks.

Also with modding everyone uses java 8 update 221, so make sure u check this out with that version of java.

wander why mojang cant enable multi core on server and client, every single pc on the planet now is multi core. why cant they upgrade that?

Heres a simple SMP earth map that simple server cant run
mediafire.com/file/ci93do7wrwh51ev/Earth.zip/file

i can tell you, its trees. if ppl have massive tree farms the decaying leaves will freeze up the server, this bug doesnt appear to be happening in single player tho.

it also seems to happen when world save of overworld is greater than 10 gigs. any SMP earth thats pre-gen will do this. reminder its not a crash that happens its a deadlock.

whats odd is in f3 mode TX number runs from 1-20 never going above 20, but i dont know how to check tick rate cuz there is no command for it like how forge has it.

Set max-tick-time in server.properties to a value higher than 60000 or to -1

if i used -1 the server had massive memory leak with excessive cpu usage. the map im using is only 20k blocks wide and 10k block height.

i dunno why this bug is flagged as resvoled/fixed which its not lol, and im ONLY one on the server.