vwemirror/BT411
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Defer RunMission until the mission load is ready (silent launch crash)

Browse Source 
The relay fires the RunMission pair a fixed 20s after the egg ACK -- but
the ACK happens at egg RECEIPT, and a long mission load (glass + dev
gauges on a busy box measured ~50s) is still in LoadingMission when the
launch lands.  L4Application::RunMissionMessageHandler's default case
Fail()ed on that state -- an abort() the 1995 code could afford because
the real console launched operator-paced -- which presented as a SILENT
crash at mission start (c0000409, no WER record; cdb stack:
ucrtbase!abort <- RunMissionMessageHandler <- RoutePacket; 3/3
reproducible; matches the field report's 464 crash that died
mid-LOD-load).

The default case now DEFERS: re-post the message to ourselves at +1s
(the VehicleDead re-post pattern) until the ladder reaches
WaitingForLaunch, bounded at 120 deferrals so a truly wedged load still
surfaces the original Fail.  Verified: the crashing console-shaped run
deferred 104x through its ~50s load, then launched, rendered (scene
LIVE) and ran clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
arcattack
2026-07-22 17:19:28 -05:00
co-authored by Claude Opus 4.8
parent 66f22fb923
commit 638cfca18d
2 changed files with 37 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
context/multiplayer.md
+13
View File
@@ -412,6 +412,19 @@ phase). Plan: `~/.claude/plans/partitioned-snuggling-piglet.md`.
survivors registered under remapped ids and ran the mission. Auto (CLI) mode keeps the
full-roster behavior. Caveat: `sys.stdin` is None under some spawn shapes (pyenv .bat shim
pipelines) -- the stdin reader guards it; the GUI's QProcess pipe is the supported channel.
- **LAUNCH/LOAD RACE -- the silent mission-start crash (2026-07-22, FIXED) [T2]**: the relay
sends the RunMission pair LAUNCH_SETTLE_SECONDS (20s) after the egg ACK, but the ACK happens at
egg RECEIPT -- a long mission load (glass + dev gauges on a busy box took ~50s live) is still
in LoadingMission when RunMission lands, and `L4Application::RunMissionMessageHandler`'s
default case `Fail()`ed = abort = a SILENT crash (c0000409, no WER record; cdb stack:
ucrtbase!abort <- RunMissionMessageHandler <- RoutePacket; 3/3 reproducible in the
console-shaped run, and the field report's 464 crash died mid-LOD-load with the same
signature). The 1995 console never hit this state (operator-paced launches). FIX
(L4APP.cpp): the default case now DEFERS -- re-posts the message to itself at +1s (the
VehicleDead re-post pattern) until the ladder reaches WaitingForLaunch; bounded at 120
deferrals so a wedged load still surfaces the original Fail. `[launch] ... deferred +1s`
log per deferral. Verified: the crashing shape deferred 104x through a ~50s load, then
launched and ran clean.
- **PATIENT WALK-UP (2026-07-18) [T2]**: a pod dialed at a relay that isn't up yet no longer
aborts (release `Fail()` is a bare `abort()` = looked like a "crash", field report). Both the
seat request (`RelayRequestSeat`) and LAN discovery (`BT_RELAY=auto`) now RETRY (2s dials, 30