macOS: activate.sh reads a post-activation Unity teardown crash (exit 134) as activation failure and skips return_license.sh, leaking a serial activation

オープン
  • 何か問題がありますか？
#855 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
50/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
bash, github-actions, macos, unity
領域
build-system, ci-cd

調査の方向性

Start in dist/platforms/mac/steps/activate.sh, where the exit at line 69 returns $UNITY_EXIT_CODE. Then check how entrypoint.sh sources this step and where return_license.sh is called, since the early exit skips it. Done means a teardown crash after a successful activation (ULF present, or the licensing success marker in the log) is classified as success, and the license is returned on the failure path too.

索引モデルが issue の本文から書いたものです。

説明

Environment: unity-builder v4.8.2 (4423ee7) / GitHub-hosted macos-26 runner / Unity 6000.4.10f1 / serial (Pro) licence mode.

What happened. During the activation phase, Unity activated successfully - the log shows the licensing client completing and the editor beginning a normal quit:

[Licensing::IpcConnector] LicenseClient-runner channel disconnected successfully.
Exiting batchmode successfully now!
...
libc++abi: terminating due to uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument
.../platforms/mac/steps/activate.sh: line 69:  4473 Abort trap: 6  .../Unity -logFile - -batchmode -nographics -quit -serial ...
Unclassified error occured while trying to activate license.
Exit code was: 134

Unity crashed in engine teardown AFTER activation completed (the ULF existed at /Library/Application Support/Unity/Unity_lic.ulf). Two separable defects in dist/platforms/mac/steps/activate.sh:

  1. Success detection trusts the raw exit code. A teardown crash after a successful activation (not rare on Unity 6 + recent macOS images; generic std::__1::system_error: mutex lock failed class) is reported as Unclassified error occured while trying to activate license. Checking for the ULF file (serial mode) or the licensing client success marker in the log would classify this correctly.

  2. The failure path orphans the serial activation. activate.sh runs exit $UNITY_EXIT_CODE - but it is sourced by entrypoint.sh, so the exit aborts the entrypoint before return_license.sh ever runs. The activation that just succeeded server-side is never returned; the slot stays consumed until someone releases it manually in id.unity.com. On seats shared across pipelines this is an outage class, not an inconvenience. Running the return step in an EXIT trap (or tolerating the activate exit code and deciding later) would make the seat crash-safe.

v5 ships a byte-identical dist/platforms/mac/steps/activate.sh, so both apply there too.

Workaround we deployed (works, happy to turn into a PR): pre-install the editor (hub headless, changeset from ProjectVersion.txt), activate in our own step where success = ULF presence (tolerating nonzero exit codes when the ULF exists), run unity-builder with skipActivation: true, and return the licence in an if: always() workflow step with a log-marker check.

主要言語
TypeScript
スター
1.1k
フォーク
318
平均マージ
23時間 20分
マージ済み PR（30日）
4

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

game-ci/unity-builder のほかの issue

game-ci/unity-builder の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。