mojira.dev
MCPE-152718

Excessive autosaving and extreme lag

Since the release of Minecraft bedrock for PlayStation 4 the game has this problem. Every time the autosave starts the world freezes for several seconds (mobs don't move, chests don't open, inventory doesn't open, blocks disappear, can't eat, damage is delayed, etc). It feels like you're on a server and you have bad internet, but in your own world.

Edit 25 April 2024:

The problem continues to occur, so I will go into detail about it.

Basically what happens is that when the auto save is executed, the world freezes completely (every 10, 30 or 60 seconds). During this period, these things happen: 

1- You cannot interact with anything (mobs, chests, blocks, inventory, any entity, damage, eat food, etc.). 

2- The ticks freeze, so redstone, mobs, and even the day cycle stop working for several seconds.

3- Some sounds stop playing, for example: the sound of footsteps, the sound of mobs, the sound of blocks and even background music may freeze.

4- When you break or place blocks, they may return to their place or they may return to your inventory, causing you to have to break or place them again.

5- The chunks will not load or generate, so if you go too fast you will not be able to advance until the auto save finishes. (Example: Flying with elytras, riding a boat, traveling with ender pearls or even going on minecarts. In extreme cases, even walking won't give the chunks time to load.

6- As the size of the world gets bigger, the auto save lag gets worse and worse.

 

What should I do to reproduce this problem?

1- Play as usual

2- The problem will begin to intensify as the world gets larger (example: +90MB = Light lag, +300MB = Severe lag, +900MB = Unplayable lag, etc.).

3- Your world will have so much lag that it will become unplayable, so you will be forced to stop playing in your world.

 

Here's a video showing an extreme case of several minutes, but usually no more than 60 seconds: https://m.youtube.com/watch?v=QwI5SwuMj-o&feature=youtu.be

Linked issues

MCPE-190914 Still lagging while autosave. Plus random lagging moment. Resolved MCPE-194674 Freezing, ghost blocks, being pushed back Resolved MCPE-194756 Lag During Auto Save Resolved MCPE-194517 Lag spikes during autosave and just in general whilst placing blocks and breaking blocks and handling crops etc. Resolved MCPE-194958 Rubber banding and saving Resolved

Comments 23

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Is this still an issue in the latest version (1.19)? If so, can you please add it to the affected versions (or mention it if you are not the reporter).

Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

it keeps happening all the time! It seems to get worse with large worlds (my world size is 953.1MB).

Still an issue, can't even play with my son anymore, he doesn't wanna play bc of the lag from autosave. It's a shame mojang does nothing to fix this. They just put everyone's ticket as a duplicate and refer them to this comment from years ago. Everyone is having this issue, please fix it.

If you have a copy of the world available, you might like to upload a copy of it for investigation.

  • On Windows 10 you can use the Export world feature.

  • On Android or iOS you need to use a file explorer to navigate to Device storage > games > com.mojang > minecraftWorlds

  • On Xbox or Switch the only way is to upload it to a Realm, and then download the world on Windows 10 or Android/iOS. (Please do not purchase a Realms subscription just to provide a world to us - but if you have a Realm already this may be a viable option if you wish to do so.)

Here are the steps to copy a world save on PlayStation:

  1. Make sure your BLANK USB stick has been formatted to FAT32

  2. On your PlayStation, go to Settings > Application Saved Data Management > Saved Data in System Storage > Copy to USB Storage Device > Select Minecraft > Select Saved World to copy > Copy

  3. This should then copy the world save to the USB, which you can share to a file sharing site such as OneDrive, and then share the link.

If the world is larger than 10MB you can upload the world to OneDrive or a similar file sharing site, and then share the link.

13 more comments

Same problem. Bigger file size, worse the lag. In addition, there s the slow chunk loading that makes flying with elytra impossivle

Just lost my hard-core world. reached day 60 in the stronghold fighting off silverfish autosave gave me extreme a extreme lagspike for about 10 seconds then I was at the “you died” screen. progress lost and time wasted. it's ridiculous I've been playing minecraft since 2014 on console and it’s only gotten worse. i get it it's a unresolved issue. it's the same with ps4/ps5/xboxone/Xbox series. pls fix this.

I have that issue on my xbox as well, but I also have a constant lag. My game is autosaving CONSTANTLY, I mean every 5-10 seconds the autosave icon pops up. This causes me to just jitter around a bit, have small lag spikes and just makes my movement feel super janky. The only solution I have is reducing my render to the single digits which sucks, and still doesn't truly solve the problem, rather just mitigates it.

On and older 360 edition you could choose the intervals at which the game would autosave, however it would stop the game and put you on a loading screen for a dozen- two dozen seconds. Works great on single player, would kinda suck on multiplayer, but I would rather have that than the inability to play my game properly

Been away from the game for a long time, started a new world this week playing split screen on ps4. At first we experienced the occasional spike for a few seconds, but day by day the issue got worse. After the game file reached 90mb, these spikes would past in excess of 15 seconds.

Today, loaded the game in single player, game file has now reached 150mb. Each autosave would cause some sort of a spike but every 15-20 minutes, the game would completely freeze for over a minute. When my friend joined split screen, game became completely unplayable, game would freeze for well over a minute, we would get maybe 10 seconds of smooth running then freeze again. While frozen, friend killed twice and I was struck by lightning 5k blocks from spawn.

GG, world lost. Bug been open for 3 years!? Poor form

Hi, I am the original creator of this report. I am posting this new comment because, due to the migration of the bug tracker system, I no longer have access to my original account, even using the same email address.

IMPORTANT UPDATE: THE ISSUE ALSO AFFECTS PS5!

The severe lag spike issue during autosave is still present and is LITERALLY making the game unplayable for many users. I was surprised to learn from comments on my video that the problem also affects PS5, which indicates this is a deeper optimization or code issue, not just a PS4 hardware limitation (CPU/HDD).

Dear mods, please, I urge you to re-evaluate this issue. I am here after being ignored for 3 years because this is a truly critical bug. Most players don't even know the autosave is the cause of the freezes.

Detailed Description and Reproduction Steps:

  1. What Happens: When the autosave runs, the local server freezes severely, causing huge, game-breaking lag spikes. As you know (per the original report), this stops all interactions: mobs, block placement/breaking, chests, inventory, and even the game ticks (redstone, day/night cycle).

  2. Frequency & Severity: This occurs every time the autosave executes (random intervals). The strength and duration of the lag spike is DIRECTLY determined by the SIZE OF YOUR WORLD (MB/GB).

  3. How to Reproduce:

    • This problem does NOT occur on recently created worlds because the file size is too small.

    • The lag starts and intensifies after playing for some days or weeks (depending on the amount of generated chunks/world size). The bigger the world gets, the worse the lag becomes until it is unplayable.

Santiago J Taborda

(Unassigned)

1225840

Community Consensus

PlayStation

PlayStation 9.03

1.21.62 Hotfix, 1.18.12 Hotfix, 1.19.50, 1.21.0.22 Preview, 1.20.72 Hotfix, 1.20.81 Hotfix, 1.21.0, 1.21.44 Hotfix, 1.21.100

Retrieved