MCPE-37465Typing § twice crashes the game
when typing § twice the game crashes
Created Issue:
§ does evil
when typing § twice the game crashes
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10
- 1.6.0
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
Added Labels: awaiting-confirmation
Changed Summary:
§ does evilTyping § twice crashes the game
Added Labels: awaiting-response
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
Removed Labels: awaiting-response
Added Affects Versions: 1.7.0
Removed Labels: awaiting-confirmation
Added ADO: 160563
Could not reproduce in Windows 10 using 1.6.0. I tried it in chat and on a sign, using §4 and §0 formatting codes, and also using consecutive §§s.
Please give more details, including the steps to reproduce the issue. This ticket will reopen when you reply.
Another moderator pointed out that this was shown in your YouTube video. I reviewed the video and we thought that maybe it was specific to Realms. So we both tested it on Realms, but it still didn't crash.
We're wondering if it could be related to the method you used to enter the § symbol, which isn't on the keyboard. We used the keyboard ALT codes on the numeric keypad, ALT+25 and ALT+0167. What method do you use?
This issue appears to only affect certain newer devices. This happens every time §§ appears on screen. As soon as §§ appears, the game crashes, I have no clue on why this happens but I know that one of the affected devices is the new Surface Pro 6.
Why is the ticket closed as Awaiting Response? When I mentioned that it "happens every time §§ on the screen" I mean you reproduce it by putting §§ on the screen, you can even reproduce the issue by putting §§ in a Resource pack or Behavior pack manifest file.
It is closed as Awaiting Response because we are awaiting responses to the questions I asked above. Apparently nobody has read them yet.
Okay. When I'm saying you reproduce it by putting §§ on the screen, you can use any method to enter it in chat (Such as ALT+0167, or Copy and Paste) or as I mentioned above, put it in a Resource pack manifest file (I made a testing resource pack), but as I mentioned already, this only affects certain newer devices, and not older ones.
Thank you. You mentioned Surface Pro 6. What other devices have you reproduced it on? If the bug is device-specific in Win 10, it could be GPU related, so if you know what model GPUs are affected please tell us that too.
Currently just the Surface Pro 6, but I'll try some more newer devices like the Surface Laptop 2 (which if the issue is GPU related, then the Surface Laptop 2 is also affected), however, the Surface Go is unaffected.
Jensen Wade: Could you please tell us what kind of computer you experienced this on, and if you know it what GPU it was using?
Additional info: According to the Microsoft spec sheet, the Surface Pro 6 and Surface Laptop 2 both use the Intel HD Graphics 620 integrated graphics chip.
Some Surface Book 2 models are affected, and some are not. Here is a table showing which models are affected:
The reason I left the 15 inch i5 model blank is because there isn't one
According to the Microsoft spec sheet, the Surface Book 2 model i5 also uses the Intel HD Graphics 620 chip, which adds support to the GPU-specific hypothesis. However, the 15-inch i7 model uses a GTX 1060 discrete GPU. It might be that these two GPUs implement the graphics interface using a slightly different interpretation of the standards than Mojang had, which causes this bug.
We are passing this bug report on to the developers as possibly hardware-dependent. Thank you, Jonathan, for the extra testing and confirmation; it is very helpful.
Cleaning up old tickets: This ticket has not been updated recently (~1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Fixed an an older version of the game (pre-1.16)