After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773784 - splitmuxsink: failed assertion on gst-launch-1.0 ^C
splitmuxsink: failed assertion on gst-launch-1.0 ^C
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other Linux
: Normal blocker
: 1.10.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 774556 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2016-11-01 18:13 UTC by Vivia Nikolaidou
Modified: 2016-11-16 15:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vivia Nikolaidou 2016-11-01 18:13:59 UTC 
83e7182b30b24e9969d6dd028ee6a152379a5741 is the first bad commit

======

Setting pipeline to NULL ...
Freeing pipeline ...

(gst-launch-1.0:3674): GStreamer-CRITICAL **: gst_object_get_name: assertion 'GST_IS_OBJECT (object)' failed
fish: “env G_DEBUG=fatal_warnings gst-…” terminated by signal SIGTRAP (Trace or breakpoint trap)

======

Core was generated by `/home/vivia/git/gstreamer/head/gstreamer/tools/.libs/lt-gst-launch-1.0 videotes'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.

+ Trace 236798

  • #0 _g_log_abort
    at ././glib/gmessages.c line 487
  • #0 _g_log_abort
    at ././glib/gmessages.c line 487
  • #1 g_logv
    at ././glib/gmessages.c line 1296
  • #2 g_log
    at ././glib/gmessages.c line 1337
  • #3 g_return_if_fail_warning
  • #4 gst_object_get_name
    at gstobject.c line 653
  • #5 mq_sink_to_src
    at gstsplitmuxsink.c line 445
  • #6 gst_splitmux_sink_release_pad
    at gstsplitmuxsink.c line 1472
  • #7 gst_element_dispose
    at gstelement.c line 3012
  • #8 gst_splitmux_sink_dispose
    at gstsplitmuxsink.c line 283
  • #9 g_object_unref
    at ././gobject/gobject.c line 3148
  • #10 gst_object_unref
    at gstobject.c line 277
  • #11 gst_bin_remove_func
    at gstbin.c line 1827
  • #12 gst_bin_remove
    at gstbin.c line 1889
  • #13 gst_bin_dispose
    at gstbin.c line 557
  • #14 g_object_unref
    at ././gobject/gobject.c line 3148
  • #15 main
    at gst-launch.c line 1230 






Comment 1


Vivia Nikolaidou





          2016-11-01 18:16:30 UTC
        



env G_DEBUG=fatal_warnings gst-launch-1.0 videotestsrc ! video/x-raw,framerate=30/1 ! timeoverlay ! x264enc ! splitmuxsink muxer=qtmux max-size-time=120000000000 location=video%05d.mov






Comment 2


Jan Schmidt





          2016-11-02 00:19:33 UTC
        



Thanks! This fixes it for me:

commit 8ff5dd802932a6f9c33f80e2750262359797a78b
Author: Jan Schmidt <jan@centricular.com>
Date:   Wed Nov 2 11:00:13 2016 +1100

    splitmuxsink: Fix GObject warnings on shutdown.
    
    Commit 83e718 added a pad template to splitmux request
    pads, which means that GstElement now releases the pads on
    dispose, but after having removed all elements in the bin
    and unlinked them. Make sure we can handle cleanup in that case
    without throwing assertions.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=773784






Comment 3


Tim-Philipp Müller





          2016-11-16 15:31:34 UTC
        



*** Bug 774556 has been marked as a duplicate of this bug. ***