On Minecraft PE, whenever I stand on top of a barrier block, the whole screen flashes red!

whenever I’m above a barrier block my screen has red on it as I fly up,then when I get so far and stop it’s a giant barrier block, in the image I’m not even close to a barrier block

Cannot reproduce on Windows 10

Could not reproduce on Windows 10 using 1.6.0.

Are you using any texture packs? If so, can you recreate this problem without any resource packs applied?

Issue exists on iOS

On iOS barriers will render their texture very large if the player is standing on the exact middle of the barrier block. The barrier texture can be rendered many times larger than the block it exists at if the camera is looking down on it.
Steps to reproduce:
1) Go into a superflat testing world, preferably one with stuff in it.
2) Run these commands yourself:
3) /gamemode survival
4) /kill
5) Respawn, but don't move the player.
6) /gamemode creative
7) /give @p barrier
8) Hold the barrier in your main hand.
9) /setblock ~ ~-1 ~ barrier
10) /tp ~ ~ ~ ~ 80
Note that none of the commands used here have anything to do with the glitch, this was just used to center your player on the block.
Now don't move anywhere, just look down and you'll see a blotch of red. It might even cover the whole screen (or just one block).
Jump up and place another barrier block below you, so they are stacked on top of each other. Now the red should fill your screen.
Try flying straight up (never move away from where you are, though), you'll see the barrier's texture enlarge and cover a substantial amount of space. Look straight down and start slowly looking up, and watch as the barrier block's texture grows, getting very large very quickly. If you keep looking up, the texture will probably disappear before it leaves the screen.

Here is the video proving the issue: 

(The command block is here to teleport the player to the very center of the barrier)

Thanks for closing the other ticket. Maybe next time make sure to copy the information from it too.

Still exists in 1.14.20 and has existed for much longer then that even.

It also happens when standing directly under a barrier not just on top. You have to be high in the sky to see the effect though. I have found at complete random if you are flying around a massive amount of barriers it can happen at absolute random when flying beside them. I’m not sure what causes this though and can’t reproduce as it’s random. I assume they are the same bug though so I’m sure if you fixed the above and below it would also fix the beside.

We ask you to search before creating a report to avoid creating duplicate reports. When you create one anyway, we ask you to add your information to the main ticket because we don't have time to do it for you. We're just a dozen or so volunteers who do this to support the community. We usually aren't experiencing your bug and don't understand it as thoroughly as you do. It would cost us a lot of time to compare your report with the original to try and figure out if it contains any new information, and we already can't keep up with the 1000 new reports a month (about 400 of which are duplicates).

The bug tracker exists for you, not us. If you want your bug fixed, try following the reporting guidelines next time instead of snarking at the people who freely give their time trying to help you.

It wasn’t my ticket. I in fact commented on that invalid ticket, which was the reason it was closed as I bounced it to the top again getting it noticed, which was good. I’m happy you’re closing invalid dupe tickets, I often report them on the Discord to get them closed faster, but why close the invalid and mark it as such then lead people to here when the entire reason you found it was because of the version number. You knew that it effected 1.14.20 yet you didn’t add it forcing me to comment here again that it dosen’t work. This adds more strain to you as that means you have to come back to the ticket and add it in later.

If you just stumbled upon a ticket and found it was a dupe, then that’s different, but when the whole reason you found it was because of additional updated information, why waste your time and my time by not transferring that information.

Trust me I would have added it myself if you allowed me to add update information. Look at my comment history. Every update I report on over 30 tickets taking the time out of my day to help you guys test them. You’re not the only one volunteering. I’m trying to make your jobs easier. If you used some common sense maybe you’d see that.

Effects 1.14.30.