FPS remains around 32 after chunk loading or temporary FPS drops until world reload

Minecraft Bedrock has a performance recovery bug. After any temporary FPS drop (such as chunk loading or spawning many villagers), the game remains stuck at approximately 26–32 FPS instead of recovering. The only way to restore normal FPS is to reload the world.

Steps to reproduce

1. Enable Unlimited Frame Rate.

1. Create or load a normal survival world.

1. Wait until the game starts at around 60 FPS.

1. Trigger a temporary FPS drop by loading new chunks (flying, exploring, teleporting, etc.) or by spawning many villagers.

1. Wait until chunk loading finishes or remove the cause of the FPS drop (for example, kill all villagers).

1. Observe the FPS.

Expected result

After chunk loading finishes or the temporary heavy workload ends, FPS should recover to its previous value (around 60 FPS).

Actual result

FPS remains permanently around 26–32 FPS even after all chunks have finished loading or the heavy workload has been removed. Waiting does not restore performance. Reloading the world immediately restores normal FPS until another temporary FPS drop occurs.

Additional information

• Platform: iPhone 15 Plus (iOS 26.31)

• Unlimited Frame Rate enabled

• Phone is cool and battery is above 50% (not thermal throttling)

• Happens in newly created worlds and existing worlds

• Triggered by chunk loading and by spawning many villagers

• Killing the villagers does not restore FPS

• Reloading the world immediately restores 60 FPS until the next temporary FPS drop

• Similar behaviour was also observed on a Samsung device, suggesting this is not specific to iOS