v0.6.74 regression: CLI render hangs on "Initializing calibration session..." (macOS M4)

[sarichan777]

[sarichan777]

Summary

v0.6.74 introduces a regression## Summary

v0.6.74 introduces a regression where the CLI render hangs indefinitely during browser calibration on macOS M4 (arm64). v0.6.73 works fine on the same system with the same composition.

Environment

• Version: 0.6.74 (installed via npm)
• OS: macOS 15 Sequoia
• Architecture: arm64 (Apple Silicon M4)
• Chrome: 143

Steps to reproduce

1. Upgrade to hyperframes 0.6.74
2. Run any CLI render
3. Observe progress output

Expected behavior

Composition renders successfully, as it does on v0.6.73.

Actual behavior

The render starts, then prints:

Initializing calibration session...

It hangs at this line forever. No progress, no error message, no timeout. The browser process is visible but idle. The hf process must be killed manually.

Workaround

Roll back to 0.6.73: npm i -g hyperframes@0.6.73

Additional notes

This happens with every composition tested. Not specific to any project or HTML structure. The calibration step itself appears to be where the hang occurs.

[miguel-heygen]

hi @sarichan777, I've the same machine but I can't reproduce it, can you share the output of the command npx hyperframes@latest doctor?

[sarichan777]

Doctor output (0.6.74, same machine):

hyperframes doctor

  ✓ Version          0.6.74 (latest)
  ✓ Node.js          v24.10.0 (darwin arm64)
  ✓ CPU              10 cores · Apple M4 @ 2400MHz
  ✓ Memory           24.0 GB total · 6.5 GB available
  ✓ Disk             801.4 GB free
  ✓ Environment      non-TTY
  ✓ FFmpeg           ffmpeg 8.0
  ✓ FFprobe          ffprobe 8.0
  ✓ Chrome           chrome-headless-shell (arm64, mac_arm-151.0.7872.0)
  ✓ Docker           Docker version 29.5.2
  ✓ Docker running   Running

  ◇  All checks passed

All checks pass but the render still hangs at calibration. Testing again now to confirm. What else would help narrow it down?

[miguel-heygen]

can you give me the hyperframes.dev url that outputs npx hyperframes publish with the project that had that issue? That would allow me to download the zip file and reproduce the issue

[sarichan777]

Here you go:

https://hyperframes.dev/p/457deaf9-7b7d-42e1-99c4-1649a8f378fe?claim_token=bkfHE65u1lgXxLGTe-qd-Glu8ieQAlCq

That is the project that hangs at calibration on 0.6.74 but renders fine on 0.6.73.

[miguel-heygen]

looking

[miguel-heygen]

reproduced the issue @sarichan777! working on a fix

[miguel-heygen]

@sarichan777 this commit will give better observability to really fix the root issue, could you try to render it again on 0.6.75 and share the whole output pls?

[sarichan777]

Tested on 0.6.75. The calibration hang is fixed (now times out after 30s instead of hanging forever), but the render still fails with the same Navigation timeout issue. Same result with --workers 1.

Calibration log:

[INFO] Initializing calibration session...
[INFO] Still waiting for browser initialization... (30.0s elapsed)
[WARN] [Render] Auto-worker calibration failed; using conservative worker budget.

Then the render itself fails:

[WARN] Parallel capture timed out with auto workers.
Failed: Navigation timeout of 60000 ms exceeded

HDR auto-detected from the 6 video sources (HLG, BT.2020, 10-bit H.265). The log suggests --docker but that also failed previously on arm64 due to headless Chrome frame capture limitations. This composition rendered fine on 0.6.73.

[miguel-heygen]

@sarichan777 can you share again a hyperframes.dev url but this time with a self-contained folder with all the assets inside of it? Also add this flag to the render command and share the output too in the meantime--debug

[miguel-heygen]

if something fails, you can send me a google drive url of the zip file