Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-159376

High CPU usage, lag and server crash


    • Icon: Bug Bug
    • Resolution: Awaiting Response
    • None
    • 1.14.4
    • Unconfirmed
    • (Unassigned)

      I started this case in https://bugs.mojang.com/browse/MC-118106 but "[MOD] CubeTheThird", wrote a message inside which I understand that my issue has nothing to do with the ticket, so that is the reason why I create this one instead, so sorry if you want to assume it differently.
      It will be okay for me, that my case is attached to another case, as long as my case is still taken seriously, as we sit a lot of players who want to play Minecraft 1.14.4, but just can't, because of, that the server version uses so much CPU.

      My problem is that the 1.14.4 server I run uses a lot of CPU.
      I host both 1.12.2 servers and one 1.14.4 server, and if you look at the image that I have attached, it is the upper one being the 1.14.4 server with 1 player on, and the lower one a 1.12.2 server with 1 player on.
      I have chosen to strip all other things as they are not necessary to illustrate it.

      I have attached a debug report.

      The server have:
      2x Intel Xeon E5603
      Minecraft Server have 8 GB RAM
      The operating system is Windows Server 2016 64bit
      Java Version: 1.8.0_201 64bit

      Gamemode: Survival

      I get a message like this, even if no players are online:
      [16:31:37] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 2364ms or 47 ticks behind

      Sometimes the Minecraft server with 1.14.4 stops itself and reports:
      [16:42:37] [Server Watchdog/FATAL]: A single server tick took 60.00 seconds (should be max 0.05)
      [16:43:59] [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown.

      I have attached the crash report.

            Unassigned Unassigned
            jackdenstore Jack Rambusch
            2 Vote for this issue
            3 Start watching this issue