Yes, it does seem to match the description of MC-273262, except for the part where exiting the game gives an error code of -1073740940 (I just get exit code 0). Sometime after I submitted this bug report, I tested 24w13a with with java 21 instead of 17, and the lag spikes appeared, so it seems to be an issue with the default garbage collector used in java 21 (G1GC). I tried switching to a different garbage collector, and the problem went away. I did load up 1.21 to test this bug again (using default launcher settings), and it seems that it more of fps drop than a 1 sec freeze. However, testing in a default world instead of a superflat world, the problem still persists. When I tried a different garbage collector (ParallelGC) instead of the default G1GC, the problem went away.
Try this if you are having trouble:
Log out then log back in
Go to the main page (minecraft.net)
Dig the blocks (or click "explode") and open one of the chests
Click "Get the Cape"
You should get the cape
This worked for me, at least
When creating an issue for ps4/pocket edition, you need to select "Minecraft (Bedrock codebase) (MCPE)" option. Also, providing screenshots is something that you should probably do.
Affects 1.19.63
Can confirm. If you want to reproduce, delete or rename options.txt and load up the snapshot. This will create a new options.txt, which will have a default chatScale option of 0.0.
Try this: minecrafthopper.net/help/exit-code/code-1073741819/
Happened on stream: https://www.twitch.tv/cubfan135/clip/FineSparklingLocustPJSalt
I've had, for the most part, the same issue (MC-273115), posting part of my comment of that report here as well:
Only thing different is that I don't get the error code as you've described (I get error code 0).
I tested 24w13a with with java 21 instead of 17, and the lag spikes appeared, so it seems to be an issue with the default garbage collector used in java 21 (G1GC). I tried switching to a different garbage collector, and the problem went away. I did load up 1.21 to test this bug again (using default launcher settings), and it seems that it more of fps drop than a 1 sec freeze. However, testing in a default world instead of a superflat world, the problem still persists. When I tried a different garbage collector (ParallelGC) instead of the default G1GC, the problem went away.