[Bug 784769] Deadlock in ges-launch between the gst_plugin_loading_mutex and class_init_rec_mutex

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Tue Jul 11 00:50:31 UTC 2017


https://bugzilla.gnome.org/show_bug.cgi?id=784769

Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nicolas at ndufresne.ca

--- Comment #1 from Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> ---
So it's a locking order problem. Is there a way you could avoid
gst_element_factory_make() from a _class_init function ? Or maybe we could drop
the registry lock while loading an element, and retake it later (with obviously
risking loading the same element twice, but when we take back the log, we could
lookup the registry again maybe, we are already in the slow path anyway.

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


More information about the gstreamer-bugs mailing list