[Bug 788549] New: rtspconnection: needs locking mechanisms?

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 788549
           Summary: rtspconnection: needs locking mechanisms?
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: jonathan.karlsson at axis.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 360949
  --> https://bugzilla.gnome.org/attachment.cgi?id=360949&action=edit
Test case to show the issue when closing the connection while writing to it

When looking into 
https://bugzilla.gnome.org/show_bug.cgi?id=785684 and 
https://bugzilla.gnome.org/show_bug.cgi?id=771525, 

we noticed that if the rtspconnection gets closed by one thread while another
thread is writing to it, there will be errors. We also noticed that no members
of rtspconnection are protected by any locks. Is this intentional?

I have added a test case to show the situation where one thread is sending when
the other one is closing.
Is this something we should handle when providing the patch for
https://bugzilla.gnome.org/show_bug.cgi?id=785684? Maybe by adding locks, or
handling the gst_rtsp_connection_close in some other way in the new
write_vectors-method?

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