maziggy 293ebd9b3f Fix ffmpeg process leak causing multi-GB memory growth (#776) ...

When a user closed the camera viewer, the stop endpoint killed the
  ffmpeg process but never signaled the stream generator's disconnect
  event. The generator saw "process died" as a dropped RTSP session
  and respawned ffmpeg — up to 30 times per stream. The orphan cleanup
  couldn't catch these because they were still tracked as active.

  - Add per-stream disconnect events dict so stop endpoint can signal
    generators to stop reconnecting before killing the process
  - Check if stream_id was removed from _active_streams before
    reconnecting (belt-and-suspenders with the event)
  - Track frame timestamps per stream_id instead of per printer_id
    so stale detection isn't fooled by newer streams for the same
    printer
  - Reduce stale thresholds from 120s+60s to 60s+30s
  - Signal disconnect events from cleanup when killing stale streams

2026-03-24 07:49:54 +01:00

..

routes

Fix ffmpeg process leak causing multi-GB memory growth (#776)

2026-03-24 07:49:54 +01:00

__init__.py

Added screenshots

2025-11-28 10:23:59 +01:00