Skip to content

Conversation

@j0sh
Copy link
Collaborator

@j0sh j0sh commented Jan 27, 2026

Some inputs can trigger the FPS/filter pipeline to generate far more output frames than are actually decoded, leading to very long, disk-filling transcodes.

Plumb decoded frame counts into the encoder path and, for video outputs, abort with lpms_ERR_ENC_RUNAWAY when encoded frames exceed 25x decoded frames, excluding image2 inputs where expansion is expected.

The exact inputs which trigger this behavior are unknown as of now but we can construct a contrived test which reproduces the issue.

Some inputs can trigger the FPS/filter pipeline to generate far more output frames
than are actually decoded, leading to very long, disk-filling  transcodes.

Plumb decoded frame counts into the encoder path and, for video outputs, abort with
`lpms_ERR_ENC_RUNAWAY` when encoded frames exceed 25x decoded frames, excluding
`image2` inputs where expansion is expected.

The exact inputs which trigger this behavior are unknown as of now but we can
construct a contrived test which reproduces the issue.
j0sh added a commit to livepeer/go-livepeer that referenced this pull request Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants