My similar crash was probably not due to heavy RAM load or too many players.
The crash happened this morning (2019-04-29) and threw "Exception ticking world" with an identical stack trace.
There was 1 player on my virtual private server which is running Minecraft 1.14 with 4 Gigs of RAM.
The world was freshly created yesterday. The player had only loaded a few hundred chucks in a straight path away from spawn.
I don't know the CPU load, so that is a possibility.
My VPS shares a quad core Intel Xeon E3-1270 running at 3.5 Ghz with other private servers at my hosting provider.
Disk latency could also be the problem.
However, I don't have hard drive transfer rate specks or issue logs.
2018-07-17, 06:07:35 AM UTC
2019-04-29, 02:03:29 PM UTC
2019-05-04, 07:27:22 PM UTC
crash-2018-07-17_01.13.20-server.txt
crash-2019-04-29_08.49.50-server.txt
crash-2019-05-04_05.20.33-server.txt
Patrick Staight
MC-133653Patrick Staight
My similar crash was probably not due to heavy RAM load or too many players.
The crash happened this morning (2019-04-29) and threw "Exception ticking world" with an identical stack trace.
There was 1 player on my virtual private server which is running Minecraft 1.14 with 4 Gigs of RAM.
The world was freshly created yesterday. The player had only loaded a few hundred chucks in a straight path away from spawn.
I don't know the CPU load, so that is a possibility.
My VPS shares a quad core Intel Xeon E3-1270 running at 3.5 Ghz with other private servers at my hosting provider.
Disk latency could also be the problem.
However, I don't have hard drive transfer rate specks or issue logs.