Reed King

posted two videos... first shows two villagers zipping off in opposite directions when a third gets in bed next to them. Second vid, a "Super" villager flies by at dusk like superman. no idea how far away he ended up, but that "coliseum" is hundreds of blocks across.

having this issue too.... sometimes they die if they slide far enough to end up in lava or on magma. Seems to happen most when multiple beds together and other villagers walk over or around a sleeping villager to get to it's bed. the sleeping villager zips off to the west, most the time seems. sometimes they will be sleeping in a block nearby and you can see their nose poking out. i've had several die in one of my oldest villages and i have to raise them from pups, again. 😞

the video above(windows 1.16.1) taken 7/2/20 shows 3 drowned spawning in a sea of glowstone. none of the glowstone are more than 4 blocks away from each other which even in water should produce higher than light level 7 in the spaces between. fyi, directly below this are several completely dark chambers that are not producing any drowned or zombies since 1.16 update.

Happening in 1.16.1 as well

I've been watching this in my game for a few weeks. for some reason after a few days of me being in a village, one villager will stop going to bed. then in a night or two another will stop going to bed and so on. I've seen as many as 6 in a village of fifty not got to bed.  I've pushed villagers right up on to their bed and they won't get in it. the only way to fix it is to restart and as soon as the game opens they all run to bed. posted 2 pics. first had 2 not sleeping then two nights later 3 were not sleeping.

this problem is Finally fixed with Hotfix 1.14.6... so play that instead of betas. Hopefully this won't return with 1.16, that would suck. dealt with this for six months. nice to be able to travel on higher chunk loads without problems. Good Luck

i tried what Andrew said a couple posts up by changing virtual memory to system managed(was set at recommended of 3996 MB) and did seem to help overall performance of the computer but had no effect on this issue... crashed 500 blocks from start with chunks set to 40.

Refer to my post on Dec 1st, 2019 for helpful tips on Managing this issue.

What Otocin posted above is encouraging. Lets hope So. Good luck

Really wish Mojang would give a progress report on this "Bug"... more like a virus. We're all trapped till further notice, if there is any.

Even with all the precautions I've figured out, I just crashed it again. Refer to my post on Dec 1st, gives some pointers In dealing with this "till it gets fixed". Jay Wells seems to be working on it... How's it coming, Jay? UPDATED POINTERS: If you travel, switch to 8 chunks and turn off monsters, especially in the nether. close and save often when traveling. Don't go to New chunks, world killer. Good Luck to us ALL!

Yes, this is in single player world.

this is not a Bug, It's a blessing!!! if you run while breaking the block 5 blocks away you can continue breaking normal blocks at high speed, even works with 20 percent speed potion. when you hit a harder block, it'll skip but just back up and start again, you can mine large lines of block faster and more efficiently. your pickaxe lasts longer because more blocks can be broken in the "damage time" for the tool. the tool can only take a damage hit at a timed interval. Don't Fix This 😃

WAYS TO CONTINUE PLAYING UNTIL THIS BUG IS FIXED, HOPEFULLY...

First, Don't explore(create) new chunks! this problem seems to be mainly based on a cap of overall world file size... mine was at 3.1 gigs the first time it happened. The Size of your World data file at the time of the First Error IS Now your CAP, you can never exceed that without Crashing. Adding new chunks will push the limit over your cap and since new chunks can't be removed it will make your world UNPLAYABLE because you have no more cache below the cap. this affects bedrock versions from 1.11 to 1.14, including betas, realms and multiplayer. if your looking for Bees and Foxes, ONLY go to previously explored areas that are the correct biome, this is how I found foxes without messing up my world.

Keep travel minimized... Flying is a good way to cause this fault. changing Chunk Rendering to lower than 24 helps  when traveling. loading many old chunks causes a temporary ballooning of the file size that surpasses the cap and causes the error. when you reload your world the chunks outside your immediate area are not active and not in the cache anymore... thus you have an empty cache to operate in.

If traveling more than 500 blocks, quitting and saving and then reopening helps clear the cache and give you more to travel on... this is a good time to have it set to 24 chunks. Also operating in peaceful helps by not adding extra mobs to the mix, especially when traveling in the Nether(and probably the End).  fighting mobs, especially Ghasts seems to use a lot of cache.

my typical action for traveling to a work site about 300 blocks from "home" is to reduce chunks to 24, switch to peaceful, quit and save, reopen and head straight into portal (avoiding loading as many chunks by not scanning around), go to exit portal, reenter overworld and quit and save again and reopen. then doing the same when returning home.

Remove as many Blocks as possible 😉 this actually reduces the "net" size of your world which gives you more cache to operate in before hitting the cap. Air blocks use less data than filled blocks. Yes, you have to remove Tens of Thousands of blocks to reduce file size enough to be worth it. I just happened to be doing a project at first sign of this bug that was removing 6 million plus blocks(rough estimate). Although, I have caused the error when actually removing tens of thousands of blocks in between saves, since this adds to the cache size during game play. So stop and save and reopen occasionally to clear the cache.

There is loss of recent game play (30 seconds or so)when the crash happens so it's possible to loose items recently placed. I've lost 150 pumpkins at one time. you don't want to loose a shulker box full of Diamonds or Emeralds or that VERY expensive Maxed out Diamond Pickaxe or pair of Boots! Been there...

in a nut shell...

Don't load(create) New Chunks

Minimize Travel. when you travel at chunk rendering of 40 chunks you open an 80 chunk(1280 block) wide path for the entire distance. That's a lot of Data of things you won't even see that is now and forever part of your game.

Save often and keep a couple days of copies for backup and export once a week to another drive, just incase. trust me. better to go back to copy and lose a few hours than your entire world.

reduce Chunk Rendering below 24

switch to peaceful

Mine your Brains out 😛

… And have Fun and Pray that Mojang fixes this soon. 😃

Hopefully the Bees will Come to Me!

HEY MOJANG! Resolving an issue by saying it is a duplicate Does NOT fix the problem, FYI. hugs and kisses. 😉

Personal update... this issue has nothing to do with world size or available data on drive. the problem is that from the initial size of the World is that it can only grow so much, let's say one percent as an example before the crash happens. when it crashes, any extraneous cache is dumped just like when the world is closed and saved. so when you restart the world after the crash it'll be a smaller file because of that. I have had it loose some data for the previous thirty seconds but not all. for example I was laying out a long line of pumpkins(256) to convert to carved pumpkins and the crash happened. when I came back little sections of pumpkins were missing from the line. one time I lost 45 and another 150.... gone to the ethers. My solution to this is if I'm doing something that is a ways away(more than 500 blocks) I quit  and save and then reopen world which drops any cache previously stored and then do the traveling and then do a quit and save and reopen in the new place. you can do this when traveling through the nether too,  but is best in peaceful mode. Also reducing the render distance for chunks down to 24 or less helps by keeping the file size from ballooning to much with all the extra chunks loaded. I've managed to travel fair distances by this method without crashing but am always cautious. IS THIS A PAIN IN THE ASS! YES!!! but until Mojang does something about it!!! that's how you keep playing your world. they fixed in previous versions apparently and NEED to do it with 1.13.1. PLEASE! It's been over a month. thanks 😃

I was able "fix" the bell by placing a different one hanging and broke the block it was hanging from so the bell falls. it added to my inventory with the stuck bell so it showed I had two and then I was able to move them and place them. this was in windows 10. didn't have to die. good luck

that sucks... I save a copy everyday and export a copy to another drive once a week. had to go back two weeks once, lost a lot of progress but better than losing everything. there's been a lot of problems with the 1.13 update, better to not push things till this is resolved. hope you find your world somehow. sorry for your loss.

it seems that its more of an in game data ballooning situation. many people have reported this issue at much lower world data file sizes. there may be a proportional amount of data that can be added to the original file size at the time of 1.13 update, for example a 1 percent addition to the original file size. I managed to make it crash after hours of doing stuff near stronghold... broke lots of blocks. when I restarted the game it was only at 3 GB and not at the 3.1 GB threshold I had hit before. so to be safer... stay near to where your at, don't fly or travel more than 500 blocks away, STAY OUT of Nether, and run in peaceful mode, monsters inflate the data size. HOPEFULLY, Mojang will deal with this soon... all I hear are crickets

try staying close to your start point... range is around 500 blocks before error occurs and stay out of nether. its an issue with your world file size ballooning to much when you play that started with the 1.13 update. you said your in 1.12 but the error never occurred for me in previous versions.

it seems its not just a file size issue but more like if you start exploring or go into the nether the file size balloons and causes the error. I'm able to play for hours on end if I just stay local and stay out of nether. the range is somewhere around 500 blocks, I think.

refer to my report on this yesterday....with the new 1.13 update, If your world data file is larger than 3.1 gigs, you can't enter. I am lucky cause I'm right at the cusp so as long as I don't enter the nether or try to fly more than 500 blocks from stronghold my file stays under that and I can function in the game. otherwise it gives me that screen and I have to restart. still no response from Mojang. this update is having huge issues... maybe they'll have to roll back like has happened in the past.