GNOME Bugzilla – Bug 788549
rtspconnection: needs locking mechanisms?
Last modified: 2018-11-03 12:00:35 UTC
Created attachment 360949 [details] [review] 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?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/390.