Closed bkovacs-orca closed 3 weeks ago
Hi, can you please expand on how you are observing that an EOS is sent and what you consider as a kvssink
shutdown?
Hey Stefan,
Thanks for the reply. I send EOS with gst_element_send_event(pipeline, gst_event_new_eos());
, so I know for a fact it's sent, I don't observe it any other way.
I consider the pipeline has shut down, including kvssink
after the call below returns, but it's stuck here:
gst_element_set_state(pipeline, GST_STATE_NULL);
Following up on this. Do you need any more information to debug this? Thank you!
Hey @bkovacs-orca, I'll be looking into this issue with dedicated time starting next week, apologies for the delay.
@bkovacs-orca, it’s difficult to assess whether the shutdown delay originates from kvssink
solely based on its presence in your pipeline. Could you please provide logs when they become available and, if possible, run some control experiments by replacing kvssink
with other sink elements to see if the behavior persists?
Closing due to staleness
I have a Gstreamer pipeline that ends with
kvssink
, and sometimes it is taking 2 minutes to shut down after EOS is sent to the Gstreamer pipeline. In what situations is this possible? What can be the reason for this?Logging I don't have logs yet, because I don't have an easy way to reproduce this case, it happens sporadically.
Any design considerations/constraints Using the following Gstreamer pipeline: