Discussion:
[Bug 778742] New: limit max-sessions to 1 leads to service unavailable after client crashes
Add Reply
"GStreamer" (GNOME Bugzilla)
2017-02-16 06:54:11 UTC
Reply
Permalink
Raw Message
https://bugzilla.gnome.org/show_bug.cgi?id=778742

Bug ID: 778742
Summary: limit max-sessions to 1 leads to service unavailable
after client crashes
Classification: Platform
Product: GStreamer
Version: 1.x
OS: Windows
Status: NEW
Severity: normal
Priority: Normal
Component: gst-rtsp-server
Assignee: gstreamer-***@lists.freedesktop.org
Reporter: ***@zeiss.com
QA Contact: gstreamer-***@lists.freedesktop.org
GNOME version: ---

Created attachment 345922
--> https://bugzilla.gnome.org/attachment.cgi?id=345922&action=edit
vlc attached successfuly followed after crash by failed attempt

If max-sessions is limited to 1 by calling
gst_rstp_session_pool_set_max_sessions, If the client terminattes without
sending an rstp TEARDOWN message, no further sessions can be established.
The attached log was prodiced by changing the test-launch.exe on windows to set
max-sessions to 1 starting the server with the example pipeline, attaching vlc
as client and then killing it using the process explorer.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
"GStreamer" (GNOME Bugzilla)
2017-02-17 02:14:17 UTC
Reply
Permalink
Raw Message
https://bugzilla.gnome.org/show_bug.cgi?id=778742

Nicolas Dufresne (stormer) <***@ndufresne.ca> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@ndufresne.ca

--- Comment #1 from Nicolas Dufresne (stormer) <***@ndufresne.ca> ---
Could this be related to bug 770934 and bug 770935 ?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
"GStreamer" (GNOME Bugzilla)
2017-02-17 06:32:21 UTC
Reply
Permalink
Raw Message
https://bugzilla.gnome.org/show_bug.cgi?id=778742

--- Comment #2 from Keith Thornton <***@zeiss.com> ---
It doenn't seem to me to be the same problem.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
Loading...