I can confirm this as a bug. There are thousands of false pernament bans, causing absolutely everyone to quit Minecraft.
I have never expected this chaos to happen.
This is a graphics card issue. Your texture buffer is too small, causing a buffer overflow. As a result, this is not fault of Minecraft, because there is no such code that causes this. It cannot be reproduced at all on my GPU. I think this issue should be invalid.
I wasn't able to reproduce this, meaning you are using datapacks.
The screen darkens out before crashing, this is possibly because the game attempts to display a server disconnection screen with a message pointer in RAM...
If we make a zombified piglin hit a baby piglin (not adult), then piglin brutes and normal piglins will attack zombified piglins.
Somehow, I ended up reproducing this in singleplayer.
Even if we restore this bug with mods, we still won't get banned. It is even mentioned on one of server discussion!
Also, this isn't mentioned in the 22w12a changelog in launcher at all.
This isn't bannable on servers due to it being a vanilla bug.
Unable to reproduce, even with auto-clicker.
I think this issue depends on hardware read/write speed.
If this crash could happen during world generation when generating structures containing jigsaw block, it would be impossible to play Minecraft with structures enabled!
This issue has to do with the introduction of /place command, that command seem to break chunks with jigsaw blocks.
Please click "Vote for this issue" instead of commenting, because that comment might be removed.
This is due to goat horn being unintentionally the exact same ID as the delete button.
Incorrectly resolved.
This code possibly relies on block group #minecraft:water, rather that minecraft:water. Since minecraft:flowing_water is in block group #minecraft:water, it causes this mess.
Before the fix, it was possible to achieve Remote Code Execution.