During normal gameplay the frame rate repeatedly degrades in steps (30 → 20 → 15 → 12 → 10 FPS) over roughly 30–90 seconds. Opening the pause menu, entering the Dressing Room, and returning to the game immediately restores a steady 30 FPS, after which the degradation starts again. The player has to do this every few minutes.
Steps to reproduce:
Launch Minecraft on a Fire HD 10 (2023) and load an existing world.
Play normally for 1–2 minutes.
Observe FPS dropping to ~10 with stutters (individual frames up to 500–800 ms).
Pause → Dressing Room → back out → resume.
FPS returns to ~30, then degrades again.
Expected: Stable frame rate without needing to visit the Dressing Room.
Actual: Frame rate repeatedly decays to ~10 FPS until the renderer is "reset" via the Dressing Room.
Measurements (via adb during ~15 minutes of play, with 3 Dressing Room resets):
FPS measured from SurfaceFlinger frame timestamps: steady 30 after a reset, decaying to 10–12. Reproduced 5+ times; it once recovered without a reset.
Not thermal: the thermal service reported status 0 and all cooling devices at 0 throughout. CPU/GPU ~50–58 °C, skin ~44 °C, battery ~30–32 °C.
Not memory: game PSS stable at ~1.05–1.13 GB, GL mtrack ~230–270 MB, system MemAvailable ~1.7 GB, and no low-memory kills. Memory does not climb between resets.
Not CPU-limited: CPU clocks mostly at max (2.0/2.05 GHz). When FPS is low, the game threads use LESS CPU (~10–20%) than when FPS is good (~30–50%), and GPU temperature drops slightly. This suggests the render pipeline is stalling or waiting rather than being overloaded.
No other apps were using significant CPU.
The attached log shows the FPS/memory timeline with the reset times marked.
Thank you for helping us improve Minecraft! We saved your files: