Skip to content

Commit 4da6c5e

Browse files
jrusso1020claude
andcommitted
fix(engine): keep the setup-timeout hint to what it can diagnose
A scheduler.yield() polling loop starves the page, so the readiness poll never returns and the render reports a capture stall instead of this message. Drop that sentence; the hint covers animation-frame and clock waits only. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 587452a commit 4da6c5e

1 file changed

Lines changed: 1 addition & 2 deletions

File tree

‎packages/engine/src/services/frameCapture.ts‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1899,8 +1899,7 @@ export function buildZeroDurationDiagnostic(diag: HfDiagnostic, timeoutMs?: numb
18991899
"During a render, Date and performance.now stay at 0 and requestAnimationFrame " +
19001900
"callbacks wait until the first frame, so setup that awaits an animation frame or " +
19011901
"the clock never finishes. Await the library's own readiness promise instead (for " +
1902-
"Three.js, renderer.compileAsync). Do not poll with scheduler.yield(): it outranks " +
1903-
"the timers that library work runs on, so the loop never ends.",
1902+
"Three.js, renderer.compileAsync).",
19041903
);
19051904
}
19061905
if (diag.rejectedBuildReadyKeys.length > 0) {

0 commit comments

Comments
 (0)