Confirmed 1.18
I can also confirm that this seems to be fixed in pre6.
I was using a relatively high render distance, around 24, and I had the default amount of memory allocated. Pretty sure I was on 12 simulation distance.
I wasn't able to reproduce this, but I found a related issue (MC-241636) where snow golems don't die, when they actually should. Could you provide a seed and coordinates of this issue occurring?
Duplicate of MC-218803. Your graphics drivers are outdated/unsupported, refer to that bug report for more info
This occurred for me in a new survival world. I attached a recording, after pausing the game briefly, causing the world to save, the game begins severely stuttering and eventually, completely freezes.
Ruined portal chests pull from the loot table 4 to 8 times. More than one of those selections can be the same item, since they are chosen independently. In this case, glistering melons were chosen at least twice (two groups of 12).
Presumably WAI.
You should provide more information so that the issue can be reproduced. My guess is that it's quasiconnectivity but this report is incomplete.
Then those chunks were already changed to the new world height and the bottom of your world was filled with air. The upgrade system doesn't change existing blocks, only adds new ones when you change to the new world height.
Did you open the world previously in 21w42a?
I'm pretty sure this happens because you're changing the spawn chunks to your current location
This also makes pulling up out of a dive incredibly inconsistent in terms of damage. In my testing with maximum prot on my armor, launching a rocket straight up and then diving straight down and pulling up for a landing results in either no damage, or about 4-5 hearts of damage. There's no middle-ground; if I take any damage at all for the landing, it's the full amount.
Duplicate of MC-162253. Also, don't report an issue found in a modded version of the game without testing it in vanilla. This is a vanilla issue as well, but mods like optifine can sometimes introduce their own issues.
And the reason you can't report a bug on 1.17 is because outdated versions of the game are not supported.
This issue occurs on Bedrock as MCPE-129748. Of course the rendering engine is quite different but it seems feasible that both issues occur for the same (or similar) reason.
Tested with 200 signs on a superflat world, each completely full with text ("abcdefghijklmnop" on each line). I get around 120 fps when far from the signs. When the signs are not glowing, they drop my fps to about 60. After making the signs glow, it drops much further, below 20 and sometimes below 15. Was trying to make a build that requires a lot of signs, unfortunately I'll have to stick with normal ones (I can get a modest improvement with sodium, but it won't be enough for what I have planned). My GPU is a GTX 1660 Ti Max-Q if that matters
Confirmed for 1.18