The bug
If you fill a command block with ■ then the launcher crashes. The game itself (Java) remains open. It's easiest to notice the launcher crashing if you have the launcher log open, but if the launcher log is closed, you can still observe the launcher crashing by using Task Manager on windows or Activity Monitor on macOS.
To reproduce
Enable the launcher log in the launcher settings.
Launch Minecraft. (I've tested this in 1.16.5 and 21w11a.)
/give @p minecraft:command_block
Paste this symbol into the command block several times: ■
Use
ctrl
+a
on windows orcmd
+a
on macOS to select all of the text in the command block.Use
ctrl
+c
on windows orcmd
+c
on macOS to copy all of the text.Use
ctrl
+v
on windows orcmd
+v
on macOS to paste the text again. Paste several copies of the text.Repeat steps 5 through 7. This will exponentially fill up the command block. Stop repeating steps 5 through 7 when the command block is full.
Click "Done".
The launcher crashes. ❌
Attachments
Comments 5
I assume that this happens on windows too, but I have not tested it. I would appreciate it if a windows user could test this and leave a comment so that I can either add the windows launcher version to the affected versions field, or else edit the description of the report.
The reason why this happens is probably because the chunk buffer is too short, and it runs into Minecraft Launcher's RAM, possibly triggering CWE-121.
I discovered this while testing MC-220067.