Jason Richards
Assigned
Comments
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.
Steps to Reproduce:
Start launcher, click play, wait for Minecraft to come up, start a game
find PID for minecraft ( ‘ps -aef | grep “java|minecraft”’)
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.
I could certainly understand this behavior if I send a KILL signal. But it happens when a TERMINATE signal is passed it.
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.
It would be great to have this fixed. My kids get a time limit to play minecraft each day and it would be nice if the tool I wrote that monitors and enforces the limits would have the ability to ask it to shutdown cleanly. SIGTERM is the designated proper Linux way of saying “Please clean your room and shutdown gracefully”