[gstreamer-bugs] [Bug 607513] New: input-selector segfaults in g_object_notify()

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=607513
  GStreamer | gst-plugins-bad | git

           Summary: input-selector segfaults in g_object_notify()
    Classification: Desktop
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: kcannon at ligo.caltech.edu
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Created an attachment (id=151803)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=151803)
example pipeline to demonstrate segfaults (might have to let it run for a
while)

input-selector can call g_object_notify() from multiple threads.  apparently
this function is not thread-safe (!?) and the result is a segfaults in the
input-selector element.

I have not studied the problem carefully so this might be a bad solution from a
bigger-picture design perspective but within input-selector, with only one
exception, g_object_notify() is always called immediately after
GST_INPUT_SELECTOR_UNLOCK() and by moving the mutex release to after the call
to g_object_notify() the segfaults are eliminated.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.