Game freezes when chunks are loaded in singleplayer
I just upgraded from my 2012 Mac mini to a hackintosh, and on the whole my games seem to run a lot better than they used to. The only exception is Minecraft singleplayer, where the game will often freeze for ~1 second when chunks are loaded. When this happens, the F3 pie graph shows an increase of activity in display_update, and Activity Monitor shows a spike in CPU activity. It doesn't seem to matter whether the chunks are being newly generated or just loaded from memory. My OS and NVIDIA drivers are up to date, and I've allocated a solid 12GB of RAM to the game (EDIT: As per CubeTheThird's advice, I've reduced this to 6GB).
When flying around in The Void super flat preset, the FPS graph occasionally shows small spikes but stays relatively smooth. I'm not sure if these small spikes are related to the larger ones I get flying around in a normal world.
Environment
OS X 10.12.2, NVIDIA GeForce GTX 960 (2047MB VRAM), 3.5GHz Intel Core i5
Created Issue:
Game freezes when chunks are loaded in singleplayer
I just upgraded from my 2012 Mac mini to a hackintosh, and on the whole my games seem to run a lot better than they used to. The only exception is Minecraft singleplayer, where the game will often freeze for ~1 second when chunks are loaded. When this happens, the F3 pie graph shows an increase of activity in display_update, and Activity Monitor shows a spike in CPU activity. It doesn't seem to matter whether the chunks are being newly generated or just loaded from memory. My OS and NVIDIA drivers are up to date, and I've allocated a solid 12GB of RAM to the game.
Environment
OS X 10.12.2, NVIDIA GeForce GTX 960 (2047MB VRAM), 3.5GHz Intel Core i5
I just upgraded from my 2012 Mac mini to a hackintosh, and on the whole my games seem to run a lot better than they used to. The only exception is Minecraft singleplayer, where the game will often freeze for ~1 second when chunks are loaded. When this happens, the F3 pie graph shows an increase of activity in display_update, and Activity Monitor shows a spike in CPU activity. It doesn't seem to matter whether the chunks are being newly generated or just loaded from memory. My OS and NVIDIA drivers are up to date, and I've allocated a solid 12GB of RAM to the game.
When flying around in The Void super flat preset, the FPS graph occasionally shows small spikes but stays relatively smooth. I'm not sure if these small spikes are related to the larger ones I get flying around in a normal world.
I just upgraded from my 2012 Mac mini to a hackintosh, and on the whole my games seem to run a lot better than they used to. The only exception is Minecraft singleplayer, where the game will often freeze for ~1 second when chunks are loaded. When this happens, the F3 pie graph shows an increase of activity in display_update, and Activity Monitor shows a spike in CPU activity. It doesn't seem to matter whether the chunks are being newly generated or just loaded from memory. My OS and NVIDIA drivers are up to date, and I've allocated a solid 12GB of RAM to the game (EDIT: As per CubeTheThird's advice, I've reduced this to 6GB).
When flying around in The Void super flat preset, the FPS graph occasionally shows small spikes but stays relatively smooth. I'm not sure if these small spikes are related to the larger ones I get flying around in a normal world.


How high did you set your render distance? Also, it's a pretty bad idea to allocate that much memory to the game, and will (if anything) reduce performance. Even in extreme circumstances, vanilla Minecraft isn't likely to use more than ~2GB of RAM.
I set the render distance to 14 chunks; part of the reason I got a new computer was because I wanted to play on >7 chunks at a decent framerate. For the record, the freezes still happen at lower distances, just not as often since not as many chunks are being loaded. I didn't know that about the RAM, so I'll reduce it to 6GB.
I recently attempted to install Windows on a separate partition on my computer and ended up deleting the entire Mac partition, and since I'm pretty happy with the way my apps run on Windows, I don't have any plans to reinstall macOS on the machine. Because of this, I no longer have a way of testing the issue and won't be keeping it up-to-date.