Blaze dutkowsky

Yes, confirmed! Just got done exploring out from the center of my world after the update and not a single crash or message saying im out of storage space. Traveled out 6000 blocks+ and even loaded some new chunks increasing my world size past 1GB ; even finding bees for the first time in my world. All without any issues of any sort.

I can't even play my solo world either due to my world also being effected by this bug  :'(

It is a good point to make that nobody with this bug will be able to try out any of the new content in the latest updates in their world due to them having to load new chunks. sad...

That explains why I am put back 100 blocks away from where I was traveling after loading up the world again after a crash.

And thanks for the method on preventing the world from crashing.

Is it safe to still play on a world affected by this? 

Like after this bug is fixed should we continue on a backup of the world before the 1.13.0 update?

In other words, is a world affected forever if it gets this bug?

Just started happening to my world for the first time 1.13.0 update.

https://www.dropbox.com/s/d9q17wlb5iofyv1/World%20Backup.zip?dl=0

my world is now getting the same error when venturing away from the center of my world.

Only ever had this problem on 1.13.0

My world is only around 1GB. 986MB right now. And I have around 23GB on the drive I have Minecraft installed. 

https://www.dropbox.com/s/d9q17wlb5iofyv1/World%20Backup.zip?dl=0

I heard about this issue going on for about a year now, but my world is now getting the same error when venturing away from the center of my world. My world is only around 1GB. 986MB right now. And I have around 23GB on the drive I have Minecraft installed.

Have you uploaded that world from Windows 10?

Because, I have uploaded mine from the base Xbox One and can download it back on the same Xbox. (Maybe only affects the One X) But, im getting the bug and can't download it on Android. I Have not tried it yet on Windows 10 (as I do not own Win 10) and im speculating it might not work. It might only be downloadable on the platform that it was originally uploaded from.

My world is also 709.4MB on the World select and 700.6 on the Realms backup. My Android has 3.4GB of free space.

Also, when I downloaded the world in the past on previous versions on Android the 680MB world was increased to about 950MB not fully synced. And sometimes on the Xbox One when the world doesn't fully sync after loading up the game it displays the size as 1.1GB. This could have something to do with this bug maybe?

Edit: Try a wired internet connection on your Xbox if your not wired already. Downloading might be working for me on Xbox because im wired and a wired connection might effect the download.

On the 1.5.3 update, I exited my world, tried loading it back up, and my game crashed......

I'm playing on my world with this bug not loading any chunks for my world doesn't corrupt. But, im still getting the crashes sometimes when exiting the world.

So my question is, will my world be cursed with this bug even after it gets fixed since I've been playing on it and saving it with this bug active?

BTW, my world was started on the Xbox One Edition and is ~295m. And corrupted when it crashed after saving and quitting after exploring generating new chunks and the world file size surpassing 300mb

FYI, I had a realms backup of my world that's how im still playing on it after corrupting.

This issue has been mostly fixed.
The issue that your having can be found here: MCPE-25344

I can confirm this big has been fixed for me with the 1.2.6 update.....
I can now join realms and servers and then start up my personal world without any problems.

Thank you Mojang for keeping up on the bugs and hopefully by the 1.3 update the new Minecraft can run as smoothly as the Xbox One Edition, if not better.

Yep, All of this sums up exactly what happening to me except it will only load up the correct player data if I restart the game entirely and then load the world up once restarted.
Note: Joining xbox live friend's worlds will not cause this bug.

I always figured the world sizes were compressed on the new engine.

My world didn't convert with the over with the same file size and everything is intact for me and no chunks regenerated.

And Erik, yours is a different issue - MCPE-25344
https://bugs.mojang.com/browse/MCPE-25344

The new 1.2.5 update fixed it.

MINE FINALLY CONVERTED SUCCESSFULLY
No lag or any problems so far, the world successfully converted over 100% intact. After so long this has finally been fixed.

Thank you Mojang for fixing this difficult bug and having my world on the official minecraft. Thank you everyone in the bug tracker for helping me and helping squash this bug.

If the small problems that you have mentioned after converting are fixed will you convert again or will you just keep this successfully converted world?

I just tried to convert my world once again on the 1.2.6.2 beta build and it took nearly 3 hours.....
Once it got to 60% it sped up like 10x and once it finally got to 95% the conversion failed and my xbox "exploded". So now I just wasted three hours of my life and my world still is not on the bedrock edition. But, I guess its getting somewhere since it took a lot longer to convert. Honestly I think my world is just incompatible with the new minecraft....

Receipt: 2017/11/14/01:22:17-6eef317e-f2e7-bc9b-eafe-ac568c52403a