Files
hyperframes/packages
Miguel Ángel ca3bdd149b fix(producer): thread forceScreenshot to probe stage for low-memory mode (#1237)
* fix(producer): thread forceScreenshot to probe stage for low-memory mode

The render orchestrator sets captureForceScreenshot=true when low-memory
mode is active and passes it to all three capture stages, but never
passed it to the probe stage. The probe stage received the original cfg
with forceScreenshot=false, so on Linux it launched the browser in
beginframe mode — which hangs on memory-constrained hardware.

Add a forceScreenshot parameter to ProbeStageInput (matching the pattern
used by captureStage, captureStreamingStage, and captureHdrStage) and
wire it through from both the render orchestrator and the distributed
planner.

Fixes heygen-com/hyperframes#1236

* fix(producer): add lowMemoryMode→forceScreenshot bump in distributed plan + regression test

- plan.ts: mirror the renderOrchestrator's lowMemoryMode bump so that
  distributed runs on low-RAM hosts also force screenshot capture mode.
  Previously the bump was only applied in the in-process path (renderOrchestrator.ts:1598);
  plan.ts derived forceScreenshot from compileResult without the bump, leaving the
  distributed probe stage in beginframe mode on low-memory hosts (same shape of bug as #1236).
  Added TODO to unify the bump into compileStage so all paths share one source of truth.

- probeStage.test.ts: add regression test pinning that createCaptureSession
  receives forceScreenshot:true when the stage input carries it but cfg.forceScreenshot
  is false (low-memory mode override). Mirrors worker-count test shape from
  captureStreamingStage.test.ts. Two cases: override active, override inactive.

Addresses review feedback from #1237.
2026-06-06 14:07:06 -04:00
..
2026-06-06 04:19:56 +00:00
2026-06-06 04:19:56 +00:00
2026-06-06 04:19:56 +00:00
2026-06-06 04:19:56 +00:00
2026-06-06 04:19:56 +00:00
2026-06-06 04:19:56 +00:00
2026-06-06 04:19:56 +00:00