Server freezes while Preparing spawn area

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Environment:

      macOS 10.14.4
      java 1.8.0_131

    • CraftBukkit version git-Spigot-6dbf995-364b6fb (MC: 1.14 Pre-Release 5) (Implementing API version 1.14-pre5-SNAPSHOT)
    • Yes

      While loading a 1.13.2 world into 1.14-pre5, the server freezes at
      "Preparing spawn area: 0%".

      There are no exceptions and the process has to be terminated.

      Loading the world into the 1.14-pre5 Mojang server works fine and fixes the world such that it now works in spigot as well.

      I have attached the log file and a minified world that reproduces the issue.

        1. world.zip
          6.13 MB
        2. latest.log
          8 kB
        3. latest.log
          243 kB
        4. latest.log
          243 kB
        5. latest.log
          243 kB

          [SPIGOT-4720] Server freezes while Preparing spawn area

          Mara Toner added a comment - - edited

          Not fixed for me, still happening

          Mara Toner added a comment - - edited Not fixed for me, still happening

          Nico Mexis added a comment - - edited

          I can't confirm, that this is fixed. I have built the Spigot jar today and the server freezes anyway.

          Not always at 0%, but right now it's frozen at 79%:

          https://hastebin.com/osetuqewox.md

           

          Edit: It freezes even with an Upgrade via Mojang's server. But then most likely at 100%.

          Nico Mexis added a comment - - edited I can't confirm, that this is fixed. I have built the Spigot jar today and the server freezes anyway. Not always at 0%, but right now it's frozen at 79%: https://hastebin.com/osetuqewox.md   Edit: It freezes even with an Upgrade via Mojang's server. But then most likely at 100%.

          PureGero added a comment -

          You might have to open a new ticket @gerningsstedet@gmail.com, I can confirm that the issue described in this ticket has been fixed

          PureGero added a comment - You might have to open a new ticket @ gerningsstedet@gmail.com , I can confirm that the issue described in this ticket has been fixed

          Michael Klit added a comment -

          Dont know about the fix, but just tried it, and to me, nothing changed, still gets stuck between 0-100% spawn rendering.

          Doing a forceupgrade on 1.13.2
          same on 1.14 pre.
          And freezes somewhere on spawn rendering

          If I do it with the Mojang version, it works fine

          Michael Klit added a comment - Dont know about the fix, but just tried it, and to me, nothing changed, still gets stuck between 0-100% spawn rendering. Doing a forceupgrade on 1.13.2 same on 1.14 pre. And freezes somewhere on spawn rendering If I do it with the Mojang version, it works fine

          MattBDev added a comment -

          latest.log

          Hopefully my latest.log can be of some help because this issue is going to delay the release of a stable 1.14 version of plotsquared.

          MattBDev added a comment - latest.log Hopefully my latest.log can be of some help because this issue is going to delay the release of a stable 1.14 version of plotsquared.

          MattBDev added a comment -

          I can confirm that servers can freeze even when being loaded for the first time. 

          MattBDev added a comment - I can confirm that servers can freeze even when being loaded for the first time. 

          PureGero added a comment -

          I also ran it with --forceUpgrade. The upgrade was successful, but the server still froze at 0%

          PureGero added a comment - I also ran it with --forceUpgrade. The upgrade was successful, but the server still froze at 0%

            Assignee:
            Unassigned
            Reporter:
            PureGero
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: