Persistent Chunk error / Corrupted world / Wrong location spam

Wait is the chunk error there on the world named "world_before bug"? i cant check right now because I'm away from my desktop

world_before bug as per second screenshot (no chunk error)

Cant this just be your computers preformance?

It seems to be a corrupted save. Try downloading the provided world and see if you can also reproduce it.

Damn it. I had loads of progress from between world_before bug to world_144pre. Is there any way I can fix this short term (i.e with MC edit?)

Probably. But i've used MCEdit on a couple of occasions. Maybe give it a go, see how it goes.

I have the same problem , the world looks ok when you open it in MC edit , editing the corrupt area with MC edit doesn't change anything , the weird thing that even after recreating the world the problem is still there , i think we just have to build around the corrupt area 😞 ಥ_ಥ

I have the same problem. 😞 I hope this gets fixed soon.

Is this glitch on mac or windows? (or both?)
Cos i got the same problem on my mac mini, it only started when i updated to mountain lion, it did it on my newer world which i made in 1.4.6, then it happened to my fav world which has all my stuff on! It is now on all my worlds apart from my flat creative one, am i right in saying that this glitch doesn't happen on flat worlds?

Just happend to me on my test world in 13w05b. The corrupted chunk started to mass spawn zombies, so I can confirm MC-4061 aswell. Using MCEdit I found that this chunk was replaced by a chunk that is not too far away (there was redstone stuff, easy to recognize). Deleting the chunk and letting Minecraft rebuild it fixed the problem. I believe this, MC-2548 and MC-4061 are all related.

I get this all the time now at the origin chunk, or the chunk the starts at 0X/0Z coordinates. It was in 1.4.6 and 1.4.7, if I fly away and back, it gets filled in, so its a server sync issue. Relogging does fix it, so this is a different bug than the one I reported, but my bug got merged into this as a duplicate, so here I am.
I had to use mcedit to move all of my worlds far away from 0,0 to avoid this issue. I suppose normal servers arent as affected by this as creative servers like ours where everyone has flymods. To cope with this I used mcedit to edit all of our worlds to have them start at 1000,1000.
I hope this gets fixed by 1.5.

how do you fix it?

This same happened to me! I wish I knew how to fix it! 😞

This has been happening more frequently. Is there any way to reload the chunks?

This happened to me, and i jump down into the "hole"and i fall to about 2-3 blocks from the level it started on at ground, y- coord is 60, and when i disable flymode i fall at around half the speed of normal falls, and i cant place anything inside the chunk zone. Multiplayer chunk cache, if this has anything to do with it, is 439

I keep having this issue over and over on countless worlds. The only "fix" i can find is to figure out which region file that chunk lives in and delete it so the whole area re-generates.

I have yet to figure out how to "fix" it that doesnt involve losing any progress in that region.

Confirmed in 13w22a
One randomly appeared in my survival world today.
Deleting the chunk via mcedit seems to fix it.
This bug somehow duplicates chickens. (This is a serious statement.)

This can usually be fixed with F3+A , it reloads all loaded chunks

Even though i only had this in multiplayer, if my computer has low internet connection

@Nico No it does not, hence persistant. The chunk is corrupt and to fix it either MCEdit it out or use a backup.

Happened in 1.6.2 on my server, yup not fixable =3

Same to me.Badly,I cant delete my houses ,nether portal,farm chunk.And I have way TOO old backup for it.Deleting all entities seems to fix it.But it deletes my farm animals,and villagers.Maybe to copy entities and paste?For me minecraft freezes on building terrain,and in output-server.log there's a error;2013-07-31 22:59:25 [SERVER] [INFO] Starting integrated minecraft server version 1.6.2

2013-07-31 22:59:25 [SERVER] [INFO] Generating keypair
2013-07-31 22:59:25 [SERVER] [INFO] Preparing start region for level 0
2013-07-31 22:59:26 [SERVER] [INFO] Preparing spawn area: 0%
2013-07-31 22:59:27 [SERVER] [INFO] Preparing spawn area: 38%
2013-07-31 22:59:28 [SERVER] [SEVERE] Chunk file at 19,41 is in the wrong location; relocating. (Expected 19, 41, got 20, 41)
2013-07-31 22:59:28 [SERVER] [SEVERE] Wrong location! rn['Bat'/34676, l='Rauliux Villager', x=314,75, y=28,10, z=665,75]
2013-07-31 22:59:28 [SERVER] [SEVERE] Wrong location! rn['Bat'/34677, l='Rauliux Villager', x=314,75, y=28,10, z=665,75];and there's spamming much of that line.

This is a really strange problem in all Minecraft versions and snapshots, even the latest. The chunk is not corrupted but GET CORRUPTED by giving and taking wrong locations of chunks! I think this bug may never be fixed! I just duplicate by mistake. Issue MC-30525.

So there is no fix and the world has to be abandoned if not functional at normal speed?

A corrupted world is when Minecraft hiccups and plops a chunk from another world to a world. Backups may help.

Observed all the way through latest snapshot (13w42b). I'd be nice if there was a flag in server.properties to optionally reset chunks that have this problem.

Observed in 1.7.2, general release. The map was reset for this release, so everything is completely new, yet we still see these problems on occasion. Example of messages spammed to log:

[09:59:02] [Server thread/ERROR]: Wrong location! uq['Bat'/11866, l='swim3', x=53591.27, y=28.10, z=-47280.06]
[09:59:02] [Server thread/ERROR]: Wrong location! uq['Bat'/11866, l='swim3', x=53591.40, y=28.10, z=-47280.24]
[09:59:02] [Server thread/ERROR]: Wrong location! uq['Bat'/11866, l='swim3', x=53591.56, y=28.10, z=-47280.45]
[09:59:03] [Server thread/ERROR]: Wrong location! uq['Bat'/11866, l='swim3', x=53591.65, y=28.13, z=-47280.67]
[09:59:03] [Server thread/ERROR]: Wrong location! uq['Bat'/11866, l='swim3', x=53591.67, y=28.17, z=-47280.92]
[09:59:03] [Server thread/ERROR]: Wrong location! uq['Bat'/11866, l='swim3', x=53591.64, y=28.22, z=-47281.18]
[09:59:03] [Server thread/ERROR]: Wrong location! uq['Bat'/11866, l='swim3', x=53591.56, y=28.27, z=-47281.45]

Also observed in the same log:

[09:58:07] [Server thread/ERROR]: Chunk file at 3349,-2956 is in the wrong location; relocating. (Expected 3349, -2956, got 3358, -2955)

Loading the region in MCEdit (0.1.8 build 665) and opening World Info, then clicking Repair Regions fixed the problem and now I don't have the error messages.

I think I have this problem too:

-Yesterday a chunk got corrupted.
-It had loaded correctly just minutes before.
-Closing and opening the game did not solve it.
-The world has been upgraded several times, this chunk was originally generated last year.
-I never downgraded, or used editors, game mode has always been adventure
-this chunk never regenerated, as happened before somewhere else in this world, but is a grey hole. Entering it will make you fall slowly, like sinking in the water.
-loading the world takes very long time, and all loading takes 'for ever'
-many glitches, sudden change of player location, general feeling of corruption
-reverted to backup

from the log:
20:33:43] [main/INFO]: Setting user: goudensun
[20:33:43] [main/INFO]: (Session ID is token:50c38eb7da7d4b0f9db2f872380cfb4b:d11567930001402ba76a2861e3cbd606)
[20:33:44] [Client thread/INFO]: LWJGL Version: 2.9.0
[20:33:45] [Client thread/INFO]: Reloading ResourceManager: Default
[20:33:46] [Sound Library Loader/INFO]: Sound engine started
[20:33:46] [Client thread/INFO]: Created: 512x256 textures/blocks-atlas
[20:33:47] [Client thread/INFO]: Created: 256x256 textures/items-atlas
[20:33:54] [Client thread/WARN]: Unable to play empty soundEvent: minecraft:music.menu
[20:33:58] [Client thread/WARN]: Unable to play empty soundEvent: minecraft:music.menu
[20:34:00] [Server thread/INFO]: Starting integrated minecraft server version 1.7.2
[20:34:00] [Server thread/INFO]: Generating keypair
[20:34:00] [Server thread/INFO]: Preparing start region for level 0
[20:34:02] [Server thread/INFO]: Preparing spawn area: 10%
[20:34:03] [Server thread/INFO]: goudensun[local:E:f53c9bea] logged in with entity id 59 at (1325.5, 70.69999998807907, -1708.766343297474)
[20:34:03] [Server thread/INFO]: goudensun joined the game
[20:34:05] [Server thread/ERROR]: Chunk file at 88,-113 is in the wrong location; relocating. (Expected 88, -113, got 78, -109)
[20:34:05] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2740ms behind, skipping 54 tick(s)
[20:34:56] [Server thread/ERROR]: Chunk file at 88,-113 is in the wrong location; relocating. (Expected 88, -113, got 78, -109)
[20:35:34] [Server thread/ERROR]: Wrong location! we['entity.MinecartRideable.name'/210, l='Finnmuren', x=1408.17, y=67.35, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.17, y=66.55, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.17, y=66.55, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.17, y=66.55, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.17, y=66.55, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.17, y=66.55, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.17, y=66.55, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! we['entity.MinecartRideable.name'/210, l='Finnmuren', x=1408.57, y=67.35, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.57, y=66.55, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.57, y=66.55, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.57, y=66.55, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.57, y=66.55, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! we['entity.MinecartRideable.name'/210, l='Finnmuren', x=1408.77, y=67.35, z=-1799.50]
[20:35:34] [Server thread/ERROR]: Wrong location! mm['goudensun'/59, l='Finnmuren', x=1408.77, y=66.55, z=-1799.50]

I think I have this bug in 1.7.3 prerelease

Not rendered chunk appeared in my singleplayer survival game. I can't enter the chunk. It causes severe lag. After a minute or so of gameplay FPS starts dropping, game starts to lag and usage of processor increases drastically for java process (the launcher).
The development console gets flooded with such type of messages (for various mobs):

[18:01:51 INFO]: Client> java.lang.Exception: Stack trace
[18:01:51 INFO]: Client> 	at java.lang.Thread.dumpStack(Unknown Source)
[18:01:51 INFO]: Client> 	at aoo.a(SourceFile:572)
[18:01:51 INFO]: Client> 	at afs.a(SourceFile:1392)
[18:01:51 INFO]: Client> 	at mm.a(SourceFile:480)
[18:01:51 INFO]: Client> 	at afs.g(SourceFile:1346)
[18:01:51 INFO]: Client> 	at afs.h(SourceFile:1253)
[18:01:51 INFO]: Client> 	at mm.h(SourceFile:365)
[18:01:51 INFO]: Client> 	at net.minecraft.server.MinecraftServer.u(SourceFile:510)
[18:01:51 INFO]: Client> 	at net.minecraft.server.MinecraftServer.t(SourceFile:440)
[18:01:51 INFO]: Client> 	at btk.t(SourceFile:117)
[18:01:51 INFO]: Client> 	at net.minecraft.server.MinecraftServer.run(SourceFile:357)
[18:01:51 INFO]: Client> 	at lb.run(SourceFile:616)
[18:01:51 INFO]: Client> 
[18:01:51] [Server thread/ERROR]: Wrong location! xc['Skeleton'/31301, l='survival_test_startu', x=170,50, y=14,00, z=452,50]

The coords given in the last line match the problematic chunk, thus I think mobs spawned in the chunk or mobs trying to enter the chunk cause the lag.

Environment: Win 8.1 (x64), Java 7 update 45 (64-bit), i7-4770 3,4GHz, 16GB RAM, GTX760

I also observed this in 1.7.3 pre-release.

Observed on a vanilla server I run on both the snapshots leading up to 1.7, and 1.7.2 realease.

For some reason, MC-41197 is listed as a duplicate of this issue (blocks break, then re-appear). And that one's listed as "Resolved", but it is happening to me again in release 1.7.4, in Windows 7. It's consistent and ruins my attempts at a hardcore speed-run, so I had to go back to 1.7.2 for the time being.

I'm really not sure this issue and MC-41197 should be counted as the same; nobody without programming knowledge would look for this issue, if their symptom is blocks breaking, then un-breaking. This made it hard for me to attempt reporting the issue.

Thanks.

This never occured to me before, but since 1.7.4 it is happening constanly. Some corrupted chunks are fully non-solid, others experience the "stuck in invisible block" effect described further above. Most chunks luckily reload properly after logging out and back in or changing render distance multiple times, but one chunk in one particular world fails to load under any circumstances.

I noticed that the server will call Thread.dumpStack() every time it reports "Wrong Location!" which is very expensive (much lag inducing). If would be nice if Mojang would call logger.isDebuggingEnabled() (or whatever they use) before arbitrarily calling Thread.dumpStack().

Confirmed for 1.7.9. (MC-55167)

Resolved? But the hole is still there and the glitch is spreading. In that biome mine carts wont go on powered track, pressure plates don't work, chests have very delayed opening and I can't build anything because I get stuck in a sort of time warp. It started with one small area now my whole village biome is ruined and I'm concerned it's going to spread even further if I continue to play. Is my whole world of almost a years worth of intensive work destroyed?

Also getting this problem in 1.7.9, resolution involves either reverting to a backup copy and pasting changes via mcedit (or just re-doing the work) or deleting the chunk from the current world and pasting in construction from a backup. Without deleting the chunk using MCEdit, it generates continual errors as players or mobs attempt to move into the bad chunk.

When it reported:

Chunk file at 4,7 is in the wrong location; relocating. (Expected 4, 7, got 11, 15)

it actually was 4,7 and should have been kept at 4,7, not relocated!

This has happened a number of times now, very annoying and requiring many hours of rework to resolve.

I have seen this issue for the latest snapshots. I was playing Legendary by Vechs and the orange wool area had a whole chunk missing.

still in 14w28b...

still in 14w29b

Log from 14w30c, where the server seems to run fine but console log gets a lot of these:

[17:43:39] [Server thread/WARN]: Wrong location! (-9, -27) should be (-9, -28), abo['Cow'/3846968, l='world', x=-136,14, y=64,00, z=-430,88]
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Unknown Source)
at bed.a(SourceFile:641)
at bet.a(SourceFile:333)
at bet.a(SourceFile:95)
at bet.a(SourceFile:83)
at qk.e(SourceFile:133)
at qk.c(SourceFile:85)
at qk.d(SourceFile:120)
at aqa.a(SourceFile:278)
at aqa.f(SourceFile:274)
at aqa.p(SourceFile:661)
at avp.c(SourceFile:66)
at asv.b(SourceFile:421)
at ql.h(SourceFile:375)
at ql.c(SourceFile:202)
at net.minecraft.server.MinecraftServer.y(SourceFile:597)
at ph.y(SourceFile:303)
at net.minecraft.server.MinecraftServer.x(SourceFile:529)
at net.minecraft.server.MinecraftServer.run(SourceFile:445)
at java.lang.Thread.run(Unknown Source)

i get this issue in 14w30c but i dont crash or get permenet chunk errors

Persistant errors in a newly created 14w30c vanilla world.

Just happened to me on version 1,7.10. I jumped in the hole died by drowning, re spawned, but the error persisted tried minning around the hole but no blocks would generate, no mobs either. Finally the world won´t load anymore.

Still happening in 14w31a

Still happening in pre-1

same for v1.8

staying some time next to it results in "not be able to interact anymore with anything, so i can't dig/mine anymore

MCedit is helpful and to recommend.

➕ You can delete the corrupted chunk
➕ It is easy and quickly done
➖ you loose then everything that was on it (but that was already the case when it was corrupted)
➖ no guarantee, that it could happen again on the same chunk (since we don't know the reason), so don't build to large stuff on it 😉

the bug still occurs in 1.8

well this got fixed on 1.8.x, not released yet.

Maybe still occurs in 1.8.1-pre5 (according to MC-74539)

Still occurs in 1.8.1!!!
MC-74861

same happens to me

Agreed - still an issue in 1.8.1 - see MC-75375. This issue should be re-opened as it certainly is not resolved

Cannot reproduce with a fresh world created in 1.8.1. If you're still experiencing this issue, then the whole world might be corrupted.

My server running 1.8.1 just got hit by this today, console spam with:

27.01 00:57:17 [Server] Server thread/ERROR Chunk file at 108,151 is in the wrong location; relocating. (Expected 108, 151, got 100, 149)
27.01 00:57:12 [Server] Server thread/ERROR Chunk file at 105,137 is in the wrong location; relocating. (Expected 105, 137, got 101, 141)

Come on Mojang! Fix this issue already! This really messes up player's saves when it happens.

You know why this happens right? It is because minecraft has a real-time autosaving feature. It's saving all the time. If anything interferes or interrupts that process in midsave then you get a corrupted chunk from saving. But there is a solution to real-time saving errors! It's the same solution as the one for handling noise corruption in cell phone transmissions, namely: REDUNDANCY. When you try to save over a perfectly good old save for a chunk DON'T overwrite it directly. Instead back up the working old save for that chunk. Hold onto these backups for about 5 minutes backwards. Then, if the game detects a missing/relocated/corrupt chunk replace it with the most recent backup and inform the player a chunk error has been detected and it was restored from a backup. This is the smart way to do it. It would mean that you don't need to back up your whole game, just carry backups for a few minutes in the past and only for the chunks that have been recently updated. This wouldn't even up file-sizes much. When you log out and close the game permanently only carry the latest backup so the game can run a check for errors when you log back in and restore if it detects this problem. Since you usually only have made changes to a few chunks in the minute before you logged out this would not increase file-sizes nearly as much as even a single backup of the whole save. They back up level.dat so they really should do the same for recently updated chunks.

Can not reproduce in minecraft 1.8 or 1.8.1

This ticket has an awful description, yet somehow it's been used as the main link for a ton of other tickets. It's been used as a dumping ground for any report that is related to chunk errors. However, I doubt ALL those dupe tickets are actually reporting the same issue.

I recently had a world that was created fresh in 1.8.7 load (after a couple save and quits) with a couple missing chunks. It was impossible to walk into the empty pit. Reloading the chunks with F3+A did not work. Exiting the world and opening it again restored the chunks to their proper state.

I'm adding a screenshot and relevant log info anyway...

[16:05:46] [Server thread/INFO]: PLAYER joined the game
[16:05:48] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2282ms behind, skipping 45 tick(s)
[16:05:49] [Client thread/FATAL]: Error executing task
java.util.concurrent.ExecutionException: java.util.ConcurrentModificationException
	at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:1.8.0_45]
	at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:1.8.0_45]
	at g.a(SourceFile:61) [1.8.7.jar:?]
	at ave.av(SourceFile:880) [1.8.7.jar:?]
	at ave.a(SourceFile:325) [1.8.7.jar:?]
	at net.minecraft.client.main.Main.main(SourceFile:124) [1.8.7.jar:?]
Caused by: java.util.ConcurrentModificationException
	at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429) ~[?:1.8.0_45]
	at java.util.HashMap$KeyIterator.next(HashMap.java:1453) ~[?:1.8.0_45]
	at ne.<init>(SourceFile:23) ~[1.8.7.jar:?]
	at amy.<init>(SourceFile:80) ~[1.8.7.jar:?]
	at bcz.c(SourceFile:50) ~[1.8.7.jar:?]
	at bdb.b(SourceFile:135) ~[1.8.7.jar:?]
	at bcy.a(SourceFile:890) ~[1.8.7.jar:?]
	at gp.a(SourceFile:81) ~[1.8.7.jar:?]
	at gp.a(SourceFile:10) ~[1.8.7.jar:?]
	at fh$1.run(SourceFile:13) ~[1.8.7.jar:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_45]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_45]
	at g.a(SourceFile:60) ~[1.8.7.jar:?]
	... 3 more

Not fixed.

I just had this in my world

[12:58:48] [Server thread/WARN]: Wrong location! (14, 33) should be (12, 30), xq
['Lightning'/104, l='Luigi's Mansion', x=227,50, y=54,00, z=532,50]

now I know what happens to my custom lightning

reopened and updated the affected versions

Appears to still be in 1.10.2. I went to the chunk error in

, but I found a chunk that was generated with new terrain (

).

[18:37:32] [Server thread/INFO]: Starting integrated minecraft server version 1.10.2
[18:37:32] [Server thread/INFO]: Generating keypair
[18:37:32] [Server thread/INFO]: Preparing start region for level 0
[18:37:33] [Server thread/ERROR]: Chunk file at -11,12 is in the wrong location; relocating. (Expected -11, 12, got -6, 13)
[18:37:33] [Server thread/WARN]: Wrong location! (-6, 13) should be (-11, 12), zd['Skeleton'/37, l='LP server', x=-85.22, y=65.00, z=216.65]
[18:37:33] [Server thread/WARN]: Wrong location! (-6, 13) should be (-11, 12), zd['Skeleton'/38, l='LP server', x=-86.51, y=64.00, z=213.31]
[18:37:33] [Server thread/WARN]: Wrong location! (-6, 13) should be (-11, 12), zd['Skeleton'/39, l='LP server', x=-87.89, y=64.00, z=213.88]
[18:37:33] [Server thread/WARN]: Wrong location! (-6, 13) should be (-11, 12), zg['Spider'/40, l='LP server', x=-86.67, y=65.00, z=216.24]
[18:37:33] [Server thread/WARN]: Tried to add entity Skeleton but it was marked as removed already
[18:37:33] [Server thread/WARN]: Tried to add entity Skeleton but it was marked as removed already
[18:37:33] [Server thread/WARN]: Tried to add entity Skeleton but it was marked as removed already
[18:37:33] [Server thread/WARN]: Tried to add entity Spider but it was marked as removed already
[18:37:33] [Server thread/INFO]: Preparing spawn area: 62%
[18:37:33] [Server thread/INFO]: Changing view distance to 16, from 10
[18:37:34] [Server thread/INFO]: __null[local:E:28b6d04d] logged in with entity id 249 at (-83.05588815617669, 65.24918707874468, 248.28641046637858)
[18:37:34] [Server thread/INFO]: __null has joined the game

Change Required
Fix Version(s) "Minecraft 1.8.1-pre1" to "None"
Reason; Affects Version contains versions after Fix Version

Fix Version(s) list contains versions in which they attempted to fix the issue.

Cool.

this just happened to me except a little bit later i found part of the chunk that had been taken out, most of it. it was a separate area of my world...

Does this still affect the current versions of Minecraft? (1.12.2, 1.13-pre3). If so, please update the ticket accordingly.

Is this still an issue in Minecraft 1.13.1?

I think this issue was already confirmed for 1.13.1 per duplicate MC-136905.

This happened to me also. I assume there is no fix for this?

Big black hole going through the world. I have logged out/in. I have traveled to the nether and back. When I jump into the hole, I will fall through the world and die. 

Since my house is partly in the hole, I have made my water elevator flow into the hole. I was able to travel down and into my mineshaft that is also affected. 

Playing bedrock edition, windows 10. V1.14.1. 

Is this still an issue in 1.15.2 or later? If it's still an issue, please provide repro steps or attach a world where the issue happens.