Producers sometimes remain after all consumers removed about go2rtc HOT 7 CLOSED

The reconnection problem in version 1.8.5 is a known issue. Solution or use version 1.8.4. Or use the master version. Or wait for the next release.

from go2rtc.

1.9.0 has new issue about unknown webrtc consumers. Maybe because dependency update. Don't know yet.

from go2rtc.

I believe that's the same issue AlexxIT identified here issue-904

from go2rtc.

Slightly different maybe? - I'm finding dead producers which maintain an rtsp connection to the camera when all consumers have gone away. Then when a new consumer connection is made, you end up with a 2nd producer. I'm monitoring bandwidth over a wireless link and can see that both producers in this scenario are pulling data from the camera.

from go2rtc.

I concur with this. I am seeing the exact same thing but for only specific cameras. This is a different issue than 904.

One of the producers where this issue happens is a python script running on an Rpi 3b+ that streams a MJPEG video using libcamera2. Even after all consumers have stopped, the ffmpeg process from go2rtc still keeps running indefinitely. Another is an ESP32Cam flashed with Tasmota that is consuming ~10GB data on my network every day due to this issue!

from go2rtc.

Btw, this issue is not present in v1.8.4 - I just tested that out. I'm staying on that version till this gets fixed.

from go2rtc.

1.9.0 is much worse for this than 1.8.5. I have a monitor running that looks for producers with no consumers then deletes/re-adds to fix it. It seems that now with 1.9.0 consumers remain as well. Disappointing - I really like the new dark mode :)

from go2rtc.