mojira.dev
MC-74858

Server keeps crashes because game tick took too long

Hi,
Since 1.8.1 and also in 1.8 (not that often though) my server keeps crashing with the error message:

[22:17:48] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2342ms behind, skipping 46 tick(s)
[22:19:19] [Server Watchdog/FATAL]: A single server tick took 60.00 seconds (should be max 0.05)
[22:19:19] [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown.

i doubled the number of cores for the VM, also doubled the RAM and also changed the java version from openjdk to oracle; but it keeps crashing. there is no specific event inside the game that triggers the crash.
the server is not even close to overload. RAM usage is about 700MB and only 1 to 2 cores are used up by 50-80%.

I attached all crash logs from today.

Related issues

Attachments

Comments

migrated
[media][media][media][media][media][media][media][media][media][media][media][media][media][media][media]
migrated

This issue is a duplicate of MC-63590. It has been linked to the original bugreport.
Please search before reporting any bugs, as it's likely that one exists already.

migrated

the mentioned workaround there only makes the server not crash - but gameticks are actually taking a lot of time (resulting in respawning blocks, missing items in chest, mobs that keep standing around and suddenly reapper and not closing / not opening doors). but there are plenty bugs already about laggy game

thats what i am seeing then all the time:

[22:45:33] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 91105ms behind, skipping 1822 tick(s)
[22:45:40] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 6953ms behind, skipping 139 tick(s)

migrated

(Unassigned)

Unconfirmed

Minecraft 1.8.1

Retrieved