pipeline deadlock issue

Wim Taymans wim.taymans at gmail.com
Tue Feb 22 04:08:47 PST 2011

On 02/22/2011 01:00 PM, Farkas Levente wrote:
> On 02/16/2011 09:54 AM, Farkas Levente wrote:
>> On Tue, Feb 15, 2011 at 14:42, Kocsis Tibor<ikt011 at gmail.com>  wrote:
>>> Hi,
>>> I have a source element that produce me 10 buffer in a hour (I'm
>>> recording with 10 frames per hour). If i have a pipeline for that, and
>>> press ctrl+c in the 12th minutes, the pipeline still freeze for 8
>>> minutes, until the next frame arrives and the EOS message. Is there
>>> any way to avoid this 8 minutes? I have similar issue with network
>>> cameras, if I have network loss, the pipeline will stay in a kind of
>>> deadlock until the timeout signals take their actions and stop the
>>> pipeline. I can't stop the save, set elements to null, do some
>>> padblock etc until that, or is there a way to do one of these actions
>>> during the freeze?
>> it's a problem for us.
>> is it true that the events and other control messages are always goes
>> with the buffers?
>> ie. is it possible to send them asynchronously/independently from the buffers?
>> regards
> hi,
> anybody from the core team can comment this?
> thanks.

Events can go independently from buffers when the SERIALIZED flag is 


More information about the gstreamer-devel mailing list