-
Bug
-
Resolution: Unresolved
-
None
-
Minecraft 1.13, Minecraft 18w30b, Minecraft 18w31a, Minecraft 1.13.1-pre1, Minecraft 1.13.1, Minecraft 1.13.2-pre1, Minecraft 1.13.2-pre2, Minecraft 1.13.2, Minecraft 18w43a, Minecraft 18w43b, Minecraft 19w11b, Minecraft 19w12b, Minecraft 19w13b, Minecraft 19w14a, Minecraft 19w14b, Minecraft 1.14 Pre-Release 1, Minecraft 1.14 Pre-Release 2, Minecraft 1.14 Pre-Release 3, Minecraft 1.14 Pre-Release 4, Minecraft 1.14 Pre-Release 5, Minecraft 1.14, Minecraft 1.14.1 Pre-Release 1, Minecraft 1.14.1, Minecraft 1.14.2 Pre-Release 1, Minecraft 1.14.2 Pre-Release 2, Minecraft 1.14.2 Pre-Release 3, Minecraft 1.14.2 Pre-Release 4, Minecraft 1.14.2, Minecraft 1.14.3 Pre-Release 2, Minecraft 1.14.3 Pre-Release 3, Minecraft 1.14.3 Pre-Release 4, Minecraft 1.14.3, Minecraft 1.14.4 Pre-Release 1, Minecraft 1.14.4 Pre-Release 2, Minecraft 1.14.4 Pre-Release 3, Minecraft 1.14.4 Pre-Release 4, Minecraft 1.14.4 Pre-Release 5, Minecraft 1.14.4 Pre-Release 6, 1.14.4, 19w39a, 1.15.2, 20w11a, 20w15a, 20w19a, 20w22a, 1.16.2, 20w49a, 1.16.5, 21w06a, 21w08b, 1.18.1, 1.19, 1.19.2, 1.19.3, 1.19.4 Pre-release 4, 1.19.4, 1.20.1 Release Candidate 1, 1.20.1
-
Confirmed
-
Save Data, UI
-
Normal
-
Platform
Hi. Whenever I optimize a large world Minecraft will freeze for me while doing the necessary backup.
Steps to Reproduce:
- Click on Optimize World (1.12 world)
- Click 'Backup and Load'
- See how Minecraft will freeze after a while.
OR:
- Click on Edit World
- Click 'Make Backup'
- See how Minecraft will freeze after a while.
For the test purpose I used the Białowieża Forest map showcased on Minecraft.net some time ago. This world is about 18GB large (~8GB bigger than our average server worlds). It will however finish doing the backup after a while and then start to run the chunk upgrade process which runs smoothly again.
I've also uploaded a picture showcasing the problem. Yeah, my CPU is at 99%, but Minecraft had two full threads and about 10% of my CPU for this task so this shouldn't be a problem (while the OS drive and the drive Minecraft is installed on had also little work to do). The problem here seems to be (just guessing) that the backup process is being done in the same thread as the render thread instead of a worker thread.
