Discussion:
[Bug 795350] New: gst_rtsp_client_close raise CRITICAL
"GStreamer" (GNOME Bugzilla)
2018-04-18 09:34:24 UTC
Permalink
https://bugzilla.gnome.org/show_bug.cgi?id=795350

Bug ID: 795350
Summary: gst_rtsp_client_close raise CRITICAL
Classification: Platform
Product: GStreamer
Version: 1.14.0
OS: Windows
Status: NEW
Severity: normal
Priority: Normal
Component: gst-rtsp-server
Assignee: gstreamer-***@lists.freedesktop.org
Reporter: x-***@foxmail.com
QA Contact: gstreamer-***@lists.freedesktop.org
GNOME version: ---

I want to dynamicly stop the rtsp-server while the pipeline is running.
gst_rtsp_client_close() is used to close the streaming client. But I got the
warning below:

GLib-CRITICAL **: g_main_context_unref: assertion 'g_atomic_int_get
(&context->ref_count) > 0' failed

I found gst_rtsp_client_finalize() is invoked firstly and unref the main
context. The gst_rtsp_client_close() do the same thing and raise the critical
warnning.

If GST_DEBUG=rtspclient:5 is set, the debug log will consoled and my
application run correctly, where gst_rtsp_client_finalize() is invoked later.

I think the problem may be similar to
https://bugzilla.gnome.org/show_bug.cgi?id=790909

Any idea?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
"GStreamer" (GNOME Bugzilla)
2018-11-03 15:41:59 UTC
Permalink
https://bugzilla.gnome.org/show_bug.cgi?id=795350

GStreamer system administrator <***@gstreamer.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |OBSOLETE

--- Comment #1 from GStreamer system administrator <***@gstreamer.net> ---
-- 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-rtsp-server/issues/41.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
Loading...