I have experienced this issue in my realm in versions 1.7 and 1.8. It actually seems to be getting worse for me.
It only seems to happen to me when I am exploring distant areas on horseback. I always have a locator map in my off hand when exploring like this. When it does happen, the world goes really haywire:
Mob movement slows to a crawl (this happens quite often anyway)
Mobs are not necessarily positioned where they are drawn (eg. I get hit by a husk that appears to be out of range)
When I managed to shoot and kill a mob beyond the "invisible wall", its drops flickered rapidly.
Logging out and back in will fix the issue temporarily.
We have seen this issue in our realm. One player saved an quit inside his base and when he returned he spawned on top of it.
I have see the "flash of white" version on two of my Windows 10 PCs with Minecraft version 1.7.0. One is an Intel CPU with an NVIDIA graphics card and I don't recall the internals of the other (used by my kids).
This issue has cleared up for me and my household. We are all able to purchase coins again. Thanks!
I checked my on my windows 10 phone and it has the same issue. At this point I have tried 3 different devices (2 computers and a phone) and 3 different accounts (2 in a family and one not) and have only received the error described in this ticket.
I am a developer too – please let me know if there is additional evidence I may be able to provide.
I am having exactly the issue described here on two different computers (and different user accounts) in my household. I purchased coins on November 7th for myself (so I know it worked recently) but am now unable to do so for either my son or myself.
There is definitely a stark performance difference between the Windows and Linux version though I am still trying to work out an apples-to-apples test that I actually have time to demonstrate.
Trevor Keniski: It is nice to see that someone else is working on this as well. What I have found is that the problem really shows itself if you turn up the tick speed then add a second player to the game. The first player to join a game seems to get priority treatment.
On Windows, even with the tick speed cranked you will be hard pressed to notice any side effects.
On Linux, if you turn the tick speed up much then every player after the first one is likely to have a terrible experience. One of the CPU cores will be pegged all the time, mobs will move in small increments and everything will stutter in general. On my Linux server with a Ryzen 9 3950X, setting the tick speed to 50 will easily cap one CPU core and present issues for the second player.
I caught on to this when I moved a game that my wife was hosting on her Core i5-8400. Her and my two kids were playing at a tick speed of 150 with no issues. After moving the game to the Linux server (the Ryzen 9 3950X) we had to turn the tick speed down to 10 to make it playable again. I suppose I should also note that all of our games have a 10 chunk simulation distance.
I am surprised that Mojang isn't all over this issue already as I strongly suspect it is hindering the performance and scalability of realms.
Moderator: If you think this belongs in a new ticket then I will be happy to create one. Thanks!