[Bug 693065] New: [GstPipeline] Seeking on pipeline with NULL clock fails assertion

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=693065
  GStreamer | gstreamer (core) | 0.10.36

           Summary: [GstPipeline] Seeking on pipeline with NULL clock
                    fails assertion
    Classification: Platform
           Product: GStreamer
           Version: 0.10.36
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: natezb at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


I first posted about this on the gstreamer-devel mailing list:
http://lists.freedesktop.org/archives/gstreamer-devel/2013-January/039223.html

What follows is mostly a rehash of that post.

When I create a pipeline and tell it to gst_pipeline_use_clock(..., NULL) and
later call a flushing seek, I get a "GStreamer-CRITICAL **: gst_object_ref:
assertion `object != NULL' failed". Removing the _use_clock() call eliminates
this problem. Using gdb, I can see that the problem comes when
gst_pipeline_change_state() tries to gst_object_ref(cur_clock) in
gstpipeline.c:422 (in gstreamer 0.10.36).

I've made a simple patch that inserts a null-check, which fixes the issue. I'll
attach this shortly.

This problem also seems to exist in the 1.0 branch, judging by the source code.

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