Open bug report

Monitor takes stall mid-recording (no frames for 45+ min) and stay 'recording'

John Lauer · 22d ago

ab 2.1.184, Windows 11, one 4K monitor (3840x2160 at 200 %), NVIDIA GPU. 2026-10-19.

Monitor takes (desktop_record_start {"monitor":0, "fps":30, "keep":true}, and the same via Hydrogen's /recording/native/start {"source":"screen"}) stop receiving frames mid-take while the screen is visibly changing (an AI chat streaming text, webviews updating):

take started last frame status afterwards
desktop-m0-20261019-014212.mp4 01:42:12Z ~01:57Z recording, "No new frame from Windows for 4879s"
desktop-m0-20261019-021514.mp4 02:15:14Z 02:15:26Z (12 s in) recording, "No new frame from Windows for 2899s", file stuck at 26 MB

Both stayed in state recording until stopped by hand, so nothing tells the caller the film is gone; about 55 minutes of a long demo were lost. A take started at 03:09Z on the same screen is fine. The Hydrogen window relaunched itself (auto-update) at least once in that window, which may be the trigger (the capture item didn't report closed).

Asks:

  • When lastFrameAgoMs passes a threshold while the desktop isn't idle (input or a window repaint seen), re-create the capture item automatically, or end the take with a clear state (e.g. stalled) so callers can react.
  • Surface stalls through notify_events.

Related: #230 (closed), #245.

0 Replies

Log in to reply.