appsink: Add a client timeout, and handle eos separately

If no chunks are written to a client for 10 seconds, we end that stream and
clean it up. This is currently happening due to a bug, but might happen due to
bad/slow clients as well.

Instead of handling EOS from null samples, handle EOS through the signal
handler. This is a more reliable way of handling EOS, and also works when the
whole pipeline is torn down because the PUT stream ended.

1 files changed, 5 insertions, 3 deletions

diff --git a/src/lib.h b/src/lib.h
index 14ec096..26cb770 100644
--- a/src/lib.h
+++ b/src/lib.h
@@ -32,11 +32,13 @@ struct _TranscodeServerCtx {
 
 struct _TranscodeClientCtx {
   SoupMessage *msg;
-  GstElement *appsink;
+  GstElement *appsink; /* We hold an extra ref to this */
   GstPad *ghostsinkpad;
+
   GMutex can_write_chunk;
-  gulong first_sample_handler_id;
-  /* The transcode server context */
+  guint timeout_handler_id;
+  guint seconds_since_write;
+  /* The transcode server context; we don't hold a ref to this */
   TranscodeServerCtx *server_ctx;
 };