[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gstreamer-bugs
Subject:    [Bug 762893] New: splitmuxsink critical assertion when changing  from null to ready
From:       "GStreamer" (GNOME Bugzilla) <bugzilla () gnome ! org>
Date:       2016-02-29 20:21:33
Message-ID: bug-762893-6437 () https ! bugzilla ! gnome ! org/
[Download RAW message or body]

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

            Bug ID: 762893
           Summary: splitmuxsink critical assertion when changing  from
                    null to ready
    Classification: Platform
           Product: GStreamer
           Version: 1.6.3
                OS: Linux
            Status: NEW
          Severity: minor
          Priority: Normal
         Component: gst-plugins-good
          Assignee: gstreamer-bugs@lists.freedesktop.org
          Reporter: ivan.aponte@gmail.com
        QA Contact: gstreamer-bugs@lists.freedesktop.org
     GNOME version: ---

If you create a splitmuxsink and change it to PLAYING. Then change its state to
NULL and then again to PLAYING state. A critical assertion occurs:

CRITICAL **: create_sink: assertion 'splitmux->active_sink == NULL' failed

The causing line I think is this one in create_sink function 

g_return_val_if_fail (splitmux->active_sink == NULL, TRUE);


This just means that the sink was already created I have tested it and it works
despite the critical message.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
gstreamer-bugs mailing list
gstreamer-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/gstreamer-bugs

[prev in list] [next in list] [prev in thread] [next in thread]