Kalvin

Still happening in 19w03a.
Same scenario as Matt Parkes above.

Will retest and provide exact steps in a moment.
Fixed, but found another related bug:
/setblock ~ ~ ~ minecraft:chest{CustomName:"{\"text\":\"NewName\"}"} destroy
/data get block <location>
Break chest
Throw chest as item
/data get entity
Doesn't contain custom name.
CustomName is restored on placing (as I found out)
Should I report/edit this issue ticket?

I have tried reproducing the issue in 1.12.2 and cannot. It appears to be fixed. I also was going to try it in 18w01a, but that version crashes for me with a malformed JSON exception, which is unrelated. I believe this issue can be closed if it hasn't been already - I don't know how all of this works exactly.

I did try that in my client connected to the server, but it only crashed the client. I tried doing it from the server console as well, but nothing happened.

I'm sorry, I do not know how to make the server crash. I am hosting a 1.11.2 server from my computer, and have set the `view-distance` option to 32. I can connect to it from my client and force my client to crash. How do I make the server crash so I can generate a crash log?

Okay, I uploaded the log. I also have a news update, this bug is completely different from what I first thought.

It looks like this bug is related to the game lagging. I know I said that was not the case, but I am thinking maybe 1.11 changed the way the graphics are rendered? See, I get a solid 60 FPS (limited, even) while playing Vanilla with this glitch. However, I noticed after a few tests that many things were lagging. If I place a bucket of water, it spreads in slow motion. I have a decent graphics card, a GTX 750 for the record. My CPU is also fine - a quad-core 4.1 GHz AMD processor. This bug only happens when I have my render distance up very high - around 25 - 32 chunks it progressively gets slower. As I said, though, I get a perfect 60 FPS the entire time, which is why this confused me and made me think there was no lag. It also explains multiplayer working - servers usually limit how many chunks you can load at a time.

I am thinking there is some other bug going on here, though. Shouldn't a 4.1 GHz processor be able to keep up with the world just fine? I've never heard of an issue like this in Minecraft.