Uploaded image for project: 'Spigot'
  1. Spigot
  2. SPIGOT-4756

Server stuck loading 1.14 vanilla world

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • None
    • None
    • JDK 1.8.0_212

      Ubuntu 16

      Start up: java -Xms128M -Xmx8G -jar server.jar

    • git-Spigot-0c02b0c-e879c44 (MC: 1.14)
    • Yes

      I can't get an update to work from vanilla 1.14 to spigot 1.14. The world size is 26GB.

      I've tried with and without the forceUpgrade flag and loaded a complete backup between each test. Each time I've tried the preparing spawn area gets stuck at 100% and the CPU usage drops from maximizing all cores to 10% and then stays there. 

      No plugins are present for testing purposes. 

      The server is frozen and won't accept logins or commands in console. When I kill and start it back up, it still gets stuck. 

      Not sure if this is related, but it peaks at 2170MB of ram and flattens out.

      I tried to load the 1.14 vanilla world in vanilla 1.14 pre5 and then with spigot 1.14 as well and that got stuck too.

      Starting up a 1.14 vanilla server and having a new world only 10MB in size, switching the 1.14 spigot successfully works. It seems as if this is some sort of problem with the size of the world I'm trying to update.

       

        1. 1.14 vanilla server to spigot small 10MB world.log
          13 kB
          Mitchell Sulkowski
        2. latest.log
          8 kB
          Mitchell Sulkowski
        3. screenshot-1.png
          141 kB
          Mitchell Sulkowski
        4. Screenshot from 2019-04-25 15-37-34.png
          91 kB
          Mitchell Sulkowski
        5. Screenshot from 2019-04-25 15-48-33.png
          105 kB
          Mitchell Sulkowski
        6. Screenshot from 2019-04-25 15-59-17.png
          92 kB
          Mitchell Sulkowski

            Unassigned Unassigned
            electro2560 Mitchell Sulkowski
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: