Build Failure Review · July 28, 2026

Halliburton Build 83173

Concise findings and background on why TeamCity reported failure after the Android package had already been built.

Verdict: likely a transient Unity shutdown crash.

No project compile, content, or packaging error appears in the reviewed log. The APK completed and was published before Unity crashed while shutting down an asset-import worker.

83173 / #24Failed build
0xC0000005Access violation
VM-05_BA-03Build agent
#25 runningSame commit + agent

What Happened

Failure Sequence

  1. Unity finished the Android build and generated the APK.
  2. AssetImportWorkerHW0 did not exit within the shutdown timeout.
  3. Unity force-killed the worker, reported lingering sessions, then crashed in native code.
  4. TeamCity received exit -1073741819 and marked step 5 failed.

Backgrounder

What The Code Means

-1073741819 is Windows exception 0xC0000005: a native memory access violation. In this log it occurred during Unity shutdown, not during compilation or package generation.

Practical read: if rerun #25 succeeds unchanged, classify #24 as transient. Escalate only if the same worker-shutdown signature repeats.