GNOME Bugzilla – Bug 627991
rtpmux will freeze whenever a flush is sent
Last modified: 2010-08-30 13:22:24 UTC
A bad typo in the GST_OBJECT_UNLOCK for the FLUSH_STOP case of rtpmux make it freeze whenever it tries to get the lock the next time. Here's the patch : http://git.collabora.co.uk/?p=user/kakaroto/gst-plugins-bad.git;a=commitdiff;h=8070c2e825cf8494e7f592e7cbdfac8418801bce
This looks good, will commit after freeze (unless someone wants to commit it now).
Can we get this before the next release actually ? It's a pretty obvious bugfix.
Created attachment 168838 [details] [review] rptmux patch Here's a proper patch attached. Please apply.
commit 5cc57a82f079d50a5f6daa8601e44fea3e7631eb Author: Youness Alaoui <youness.alaoui@collabora.co.uk> Date: Wed Aug 25 22:56:03 2010 -0400 rtpmux: Unlock the right mutex The mutex locked is for the 'mux' object, but we unlock the pad, which means that if the rtpmux gets a flush, then the object lock will stay locked forever, causing it to freeze the next time it tries to take it. Fixes bug #627991