error "Server process exited without calling ProcessEnding" shows up even I confirmed process ending is called in auxproxy.log with UE5.0.1 release

1

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?

thanks.

質問済み 2年前531ビュー
1回答
0
承認された回答

it's because linux server built with UE5 always returned with 139 exit code.

回答済み 2年前
profile picture
エキスパート
レビュー済み 1ヶ月前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ