-
Bug
-
Resolution: Duplicate
-
None
-
1.18 Pre-release 1
-
None
-
OS: Windows 10
Java Version: 17
CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz 3.50 GHz
Installed RAM: 32 GB
-
Unconfirmed
-
(Unassigned)
I had decided to upgrade the amount of memory allocated to Minecraft as I thought it would allow me to increase my render distance to max without getting lag , but I found that it ended up using a larger amount of memory than what the game usually uses and the game keeps crashing. This continued to occur even after I went back to last week's snapshot, returned the allocated memory to the default, and lowered my render distance to my usual of 29 or 28 it continued to use 70%-96% of the allocated memory, this even continued to occur after I restarted my PC. It would also appear that I'm only experiencing this issue on the snapshots and pre-release, as when I load up 1.17.1 everything is fine. Also when I open task manager it displays a CPU usage as well. I only managed to fix the issue after returning my world to a backup right before I updated it to the Pre-release, and it also appeared to only affect one of my worlds.
- duplicates
-
MC-239682 Out of memory crash: World generation exhausts Java heap space
- Resolved