[gstreamer-bugs] [Bug 158162] opt deadlock

bugzilla-daemon at bugzilla.gnome.org bugzilla-daemon at bugzilla.gnome.org
Fri Dec 3 09:44:52 PST 2004

GStreamer | gstreamer (core) | Ver: HEAD CVS

rbultje at ronald.bitfreak.net changed:

           What    |Removed                     |Added
  Attachment #33728|0                           |1
        is obsolete|                            |

------- Additional Comments From rbultje at ronald.bitfreak.net  2004-12-03 12:44 -------
Created an attachment (id=34460)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=34460&action=view)
possible fix

Attached patch adds a 'run-only-me' property to the _run_queue() function in
opt. _run_queue() is called from two different functions, either
schedule_chain() and the opt _get_wrapper(). In the last case, you don't
actually want to schedule any other elements but the one in the get-group. In
the first case, you don't care which are scheduled. The reason for this
distinction (I think) is that you can 'queue' chain data, whereas gets need to
be handled as quickly as possible, without recursing into any other groups
(which also causes the above deadlock).

I didn't look too closely, didn't run testsuites (bad me), but the above
pipeline (filesrc location=filewithapetags.mpc ! decodebin ! alsasink) works
for me now.

------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the Gstreamer-bugs mailing list