Make the engine wait for a ladder that started ahead of it, and mark the hand-over to the main loop - #71
Merged
Conversation
…the hand-over to the main loop build-1933ad8's two launches both went silent within a second of ENGINE FAILURE — the first on the ladder's first rung, the second, walking ahead of the engine, seven rungs in — with the probe thread, the permission probe's thread and the failure screen's heartbeat stopping together and the trail writer healthy at the last page load. Whatever ends these launches is timed off the engine's failure, not off any rung, and the early walk's head start was the half-second the engine took to fail. - On an install where the walk started ahead of the engine, OnCreate waits for it (NativeProbe.WaitForWalk, 90 s at most) before TryStartEngine, and says so. - Two trail markers around the hand-over: the last line OnCreate writes after the failure screen, and an EcoreMainloop.Post that writes when the loop first runs. - AppDomain.UnhandledException in Program.Main writes thread, type, message and stack before the abort; Main's catch only ever saw its own thread. Issue 17. docs/INTERNALS.md has the reading of the report.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What the Q80 said on build-1933ad8
Two launches on a fresh install, three pages (issue 17, 2026-09-05 15:05). The first ran the ordinary order and ended on the ladder's first rung. The second found the ledger, walked ahead of the engine, and answered seven rungs —
control:anon-exec = ok(the rung the launch before had "ended" on), thedata/copy, the engine header, andres/open/header/read/exec (EPERM, fourth time) — before ending on the/proc/self/fdretry.trail write:was healthy on every page.Both launches went silent within a second of
ENGINE FAILURE, with the probe thread, the permission probe's thread and the heartbeat stopping in the same second. The early walk's head start was the half-second the engine took to fail.Changes (all
src/elm+Program.cs)StartEarlyIfUnfinishedstarted it,OnCreatewaits onNativeProbe.WaitForWalk(90 s at most) beforeTryStartEngine, and writes what happened either way.failure screen drawn — OnCreate returns, the main loop starts, andmain loop: first iteration ranviaEcoreMainloop.Post. A trail ending between them ends in the loop's first iteration.AppDomain.UnhandledExceptionhandler inMain: thread name, type, message, stack.Dropwaits for the disk, so the line lands before the abort.Verified
tools/probeladder/run.sh— 10 shapes pass (earlynow usesWaitForWalk)../build.sh all— all five packages build.docs/INTERNALS.md: new section Whatever ends the launch is a second behind the engine;build-<next>placeholders filled by the follow-up.