Skip to content

Program render stalls ~100 ms when a take opens a media clip (4-6 delivery slots with no frame) #724

Description

@iamfatness

Found during #703 / #723 (2026-09-30).

When a take brings a media clip on air at stream start, Program rendering stops for about 100 ms. The program buffer logs 4–6 consecutive stage=source misses (e.g. delivery slots 26–31), and the next rendered frame lands 4–6 slots later than its frame number.

  • A/V impact: fixed separately in #538 Stamp stream video by delivery slot, not render frame number #723. Stream video is now stamped by delivery slot, so the stall is a PTS gap, not an A/V offset.
  • Remaining impact: a visible ~100 ms freeze on Program and every output, and 4–6 missing frames. That fails the 60 fps per-frame delivery requirement in CLAUDE.md.

Repro:

Next step: find where the render thread blocks when the media source opens (MediaTransports apply / first decoder frame / texture creation). The likely fixes are to move that work off the render thread, or hold the last frame without losing slots.

Activity

  1. added 2 commits that reference this issue on Oct 1, 2026
  2. iamfatness commented on Oct 1, 2026

    @iamfatness
    OwnerAuthor

    Fixed in #731 and shipped in beta-2026-10-01-43b33b9: shared-texture exports are created off the render thread. Harness: 5 of 5 runs missed slots before, 0 of 6 after. Leaving open for owner acceptance and because the 4-6 slot stall first reported was not reproduced (two slots per event were).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogRanked in docs/BACKLOG.md

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions