error "Server process exited without calling ProcessEnding" shows up even I confirmed process ending is called in auxproxy.log with UE5.0.1 release
from this image, we can see that the game session, 53E1A6ED-EB5B-418A-89E8-D773682B70AB in the fleet fleet-76e80f57-a589-444f-ba49-664672c2f9e6 didn't call process ending before terminate the process. But when I check the logs in auxproxy.log in /local/whitewater/Logs/, here, we can see the game session 53E1A6ED-EB5B-418A-89E8-D773682B70AB is the process fb528fcf-ac19-45d0-9750-a28bebf4da11 in the fleet instance. But from here, we do see the it has received the process ending message for process fb528fcf-ac19-45d0-9750-a28bebf4da11. And the process is closed hundreds milliseconds after "Marking process fb528fcf-ac19-45d0-9750-a28bebf4da11 as unavailable for game sessions" log is printed.
it only happens on UE5.0.1 release. Can you tell me how it determine the process closed without calling process ending? is there any other condition except process ending is called or not?
it's because linux server built with UE5 always returned with 139 exit code.
error "Server process exited without calling ProcessEnding" shows up even I confirmed process ending is called in auxproxy.log with UE5.0.1 releaseAccepted Answerasked 3 months ago
Server process exited without calling ProcessEnding()asked 4 years ago
Server process exited without calling ProcessEnding(), exitCode(-1073740940)asked 2 years ago
.NET 5 Server App on GameLift?Accepted Answerasked a year ago
No available process when using GameLiftLocalAccepted Answerasked 4 months ago
Unity server built with IL2CPP failsasked a year ago
What do I have to do after a match is over?asked a year ago
Process Substitution not working with Linux 2 bash?asked 2 years ago
Can not you call SDKInit () in a background process?asked 4 years ago
Server screenshot shows lock screen even when server is not in lockscreenasked 2 months ago