GNOME Bugzilla – Bug 675762
x264enc: Deadlock on property changes
Last modified: 2012-05-10 14:00:10 UTC
This was initially fixed using the stream lock (commit 30a0b50e9ca0d625e61f994d4f8acd022dcddf38) instead of the object lock, but this is conceptually wrong and may cause deadlock if properties are changed in paused state.
Created attachment 213749 [details] [review] x264enc: Don't set latency while holding object lock This reverts commit 30a0b50e9ca0d625e61f994d4f8acd022dcddf38. https://bugzilla.gnome.org/show_bug.cgi?id=675761
Created attachment 213750 [details] [review] x264enc: Don't set latency while holding object lock This reverts commit 30a0b50e9ca0d625e61f994d4f8acd022dcddf38.
Can also be seen at: http://cgit.collabora.com/git/user/nicolas/gst-plugins-ugly2.git/log/?h=675762-deadlock-setting-latency
commit 6814275662e3874ed63dc170335839d8cccf5f6e Author: Nicolas Dufresne <nicolas.dufresne@collabora.com> Date: Mon May 7 11:52:40 2012 -0400 x264enc: Don't set latency while holding object lock This reverts commit 30a0b50e9ca0d625e61f994d4f8acd022dcddf38. https://bugzilla.gnome.org/show_bug.cgi?id=675762