[gstreamer-bugs] [Bug 424087] [xvimagesink] crash in _setcaps() in totem

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=424087

  GStreamer | gst-plugins-base | Ver: 0.10.12

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|totem-gstreamer-            |gstreamer-
                   |maint at gnome.bugs            |bugs at lists.sourceforge.net
          Component|GStreamer backend           |gst-plugins-base
            Product|totem                       |GStreamer
          QAContact|totem-gstreamer-            |gstreamer-
                   |maint at gnome.bugs            |bugs at lists.sourceforge.net
            Summary|totem crashed with SIGSEGV  |[xvimagesink] crash in
                   |in IA__g_object_ref()       |_setcaps() in totem
   Target Milestone|---                         |HEAD
            Version|2.18.x                      |0.10.12




------- Comment #1 from Tim-Philipp Müller  2007-04-11 09:34 UTC -------
Line 1848 in gst_xvimagesink_setcaps() is:

  intersection = gst_caps_intersect (xvimagesink->xcontext->caps, caps);

I think the reference to g_object_ref() in the stack trace might be bogus.
First suspicion is xvimagesink->xcontext being NULL/garbage, but I don't see
any of the other threads doing a concurrent shutdown, so I don't know why that
would be the case.

In any case, looks like an xvimagesink issue => GStreamer.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=424087.