-
Bug
-
Resolution: Duplicate
-
None
-
Minecraft 1.14
-
None
-
[Windows 10]
I loaded a world, then exited it within 10 seconds. This world had previously been hosted over LAN, and one player other than myself has played in it.
Hardware:
* i7-6700HQ (quad core laptop CPU)
* 16GB RAM (I've set my game to allocate a minimum of 3 and a maximum of 8)
* NVidia GTX 960M 4GB (yes, I had to manually set my computer to use it)
* Minecraft is installed to the C drive, which is a 120GB M.2(ACPI) SSD.
** I have 15 GB free on this drive.[Windows 10] I loaded a world, then exited it within 10 seconds. This world had previously been hosted over LAN, and one player other than myself has played in it. Hardware: * i7-6700HQ (quad core laptop CPU) * 16GB RAM (I've set my game to allocate a minimum of 3 and a maximum of 8) * NVidia GTX 960M 4GB (yes, I had to manually set my computer to use it) * Minecraft is installed to the C drive, which is a 120GB M.2(ACPI) SSD. ** I have 15 GB free on this drive.
-
Unconfirmed
-
(Unassigned)
After exiting the world, the game entered the loading screen correctly, but never got past "Saving world." I have let it run for at least an hour so far. Clicking around on the game doesn't make it register as not responding, so I haven't received a prompt to force close it. I don't know whether or not forcibly closing the game will corrupt the world.
Normally, worlds save within 5-8 seconds at the worst, and given my hardware, this can't possibly be due to low resources. Minecraft is using 259-312 MB of RAM, gradually increasing and then returning to a lower value. This leaves me with more than enough RAM to run another instance of Minecraft 1.14, which hasn't had this problem.
- duplicates
-
- Resolved