The game crashes instead of shutting down gracefully when given a SIGTERM signal

Would MC-202209 describe your issue?

_{This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.}

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Hi There; It doesn't exactly cover it. I would assume a plethora of things are not happening when the signal is received. Saving player data would probably be one of them.

When the signal is received, the process goes away and something (maybe the launcher) pops a dialog box saying the process crashed and wants to send a bug report to Mojang.

I could certainly understand this behavior if I send a KILL signal. But it happens when a TERMINATE signal is passed it.

We do not have enough information to reproduce this issue.

Please include the following information to help us understand your problem:

Steps to Reproduce:
1. (Explain what needs to be done for the issue to happen)
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

Please also attach any needed commands, add-ons/behavior packs, data packs, resource packs, screenshots, videos, or worlds needed to help reproduce this issue.

Refer to the Bug Tracker Guidelines for more information about how to write helpful bug reports. Bug reports with insufficient information may be closed as Incomplete.

_{This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.}

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Steps to Reproduce:

1. Start launcher, click play, wait for Minecraft to come up, start a game

2. find PID for minecraft ( ‘ps -aef | grep “java|minecraft”’)

3. send SIGTERM ('kill -15 <PID>')

Observed Results:

Minecraft goes away and a dialog box pops up saying Minecraft, requesting to send a bug report to Mojang.

Expected Results:

Minecraft automatically performs the equivalent of a player saving game, exitting game, shutting down Minecraft cleanly. No crash dialog box.

Thank you for your report!
After consideration, the issue is being closed as Working as Intended.

Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.

Full Version History – Snapshot Version History – The official Minecraft feedback site

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

The “crash” is just launcher detecting non-zero exit code, so this popup is working as intended. MC-202209 still remains an open issue.

boq - thank you for your response - otherwise I would have thought the issue was just being brushed off! I tested and now see that the minecraft-launcher is popping the dialog box as a result of minecraft exit code 143.