Release notes

Videorc 0.9.74 Beta 1

Each recording's encoder is now torn down deterministically the moment its session ends. Previously the encoder loop of a finished session could keep running — still compressing 4K video with no session attached — competing with the next recording's screen and camera capture, which is the strongest lead in the "later recordings freeze" investigation. Recording starts now also wait for (and loudly report) any leftover encoder from a previous session, and a backend logging failure can no longer crash a recording in progress.

Download macOS betaAll releases

Recordings stop tripping over the previous one

  • When a recording ends, its encoder is shut down and reaped within a bounded deadline — it can no longer keep encoding in the background and steal capture bandwidth from your next clip.
  • Starting a recording now checks for leftover encoders from previous sessions, waits briefly for them to clear, and warns you honestly if one is still running.
  • A failure to write a log line (for example when the app is shutting down) can no longer crash the recording backend mid-session.

Fixed

  • macOS session teardown now stops and joins both encoder-bridge writers with a 3s deadline immediately after the muxer exits — the deterministic twin of the Windows-side join that already existed. A writer that fails to exit is detached and reported (encoder-bridge-writer-leaked) instead of silently living on.
  • Session start fences on leftover writers (encoder-bridge-writer-lingering warning after a 2s grace) so a leaked encoder can never silently sabotage the next recording.
  • The backend's log writer swallows stderr failures instead of panicking — a broken log pipe could previously abort the whole backend mid-recording.

Investigation

  • The frozen-frames collapse reproduces only with real capture devices under a live session and correlates with leftover encoder activity; these fixes remove that interference and instrument any residual leak loudly. If a recording still degrades, the session log and support bundle now name the leak explicitly.