[gstreamer-bugs] [Bug 473846] Deadlock if sink is unable to send first buffer

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Wed Sep 5 15:16:10 PDT 2007


If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=473846

  GStreamer | gstreamer (core) | Ver: 0.10.13

Wim Taymans changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wim.taymans at gmail.com
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.15




------- Comment #1 from Wim Taymans  2007-09-05 22:16 UTC -------
two problems with this program:

1) you start playback of the source before it is linked, this causes an error
if you don't manage to link the sink fast enough.

2) the fd passed to fdsink is not set to NONBLOCK, this currently makes the
write call block (and not cancelable) forever.

I think you just want to make a pipeline, set it to PLAYING, then perform a
latency query and see it deadlock.

I changed core to not take the PREROLL lock anymore when doing the query. 

        * libs/gst/base/gstbasesink.c: (gst_base_sink_preroll_queue_flush),
        (gst_base_sink_wait_preroll), (gst_base_sink_needs_preroll),
        (gst_base_sink_query):
        Protect eos and have_preroll with the OBJECT lock so we don't need to
        take the PREROLL lock when querying the latency. Fixes #473846.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=473846.




More information about the Gstreamer-bugs mailing list