[Bug 728153] New: Problem with send_lock when data in backlog and recive a teardown request.

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=728153
  GStreamer | gst-rtsp-server | unspecified

           Summary: Problem with send_lock when data in backlog and recive
                    a teardown request.
    Classification: Platform
           Product: GStreamer
           Version: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-rtsp-server
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: goran.jonsson at axis.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=274230)
 View: https://bugzilla.gnome.org/attachment.cgi?id=274230
 Review: https://bugzilla.gnome.org/review?bug=728153&attachment=274230

gst-rtsp-server patch

This when drop-backlog parameter is FALSE.
The drop-backlog parameter is intruduced in ticket
https://bugzilla.gnome.org/show_bug.cgi?id=725898

Attached file : gdb_bt

Analyz:
The handling of teardown Thread 3 (Thread 3111):  stuck on mutex 
ownd by Thread 14 (Thread 3150): . That is stuck on mutex owned by 
Thread 15 (Thread 3151):

We need to get out of do-while loop in do_send_message. The send_lock
mutex taken in do_send_data will not be unlocked if loop not end.

Solution:
Inside do-while loop check if there is any transports, if not 
break the loop.

Attached patch : breakloop.patch

-- 
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.