mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-03 12:54:29 +00:00
shouldRetryViaPinnedFallback retrying OOM was only half the fix: it reused preInversionWorkerCount/preRouterWorkerCount unmodified, which is calibration's own pick and can be >= the pinned count that just OOM'd (calibration wanting 5 while the router pinned to 3). Retrying at equal or higher parallelism than the failure isn't a remedy — it's the same bet again, and worsens the odds for this render and anything sharing the host (PRODUCER_MAX_CONCURRENT_RENDERS runs concurrent jobs in one process). resolveInversionRetryPlan/resolveParallelRouterRetryPlan now drop to workerCount=1 specifically when the retry is OOM-triggered — one Chrome page, the leanest configuration available, not just a different capture mode at the same worker count. Ordinary self-verify (blank/PSNR) retries are unaffected — those aren't memory-related, so they keep the pre-inversion/pre-router count as before. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>