[Gtk2-perl-bugs] [Bug 506301] New: GStreamer : crash after changing the audiosink of a playbin

[gnome-perl (bugzilla.gnome.org) <bug...@bu...>]

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=506301

  gnome-perl | general | Ver: unspecified
           Summary: GStreamer : crash after changing the audiosink of a
                    playbin
           Product: gnome-perl
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: general
        AssignedTo: gtk...@li...
        ReportedBy: squ...@fr...
         QAContact: gtk...@li...
     GNOME version: 2.19/2.20
   GNOME milestone: Unspecified


Please describe the problem:
After changing the audio-sink of a PlayBin element, some messages coming from
the bus can cause random crash when querying its type. I guess it's because
this message comes from the old audio-sink that doesn't exist anymore.
By the way, being able to know the source object of the message (included in
the GstMessage structure) would be nice.

I'm not sure it's a binding bug.

Steps to reproduce:
run the attached program with an audio file as argument


Actual results:
random crashes, after a random number of play/stop (1 to ~20)

Expected results:


Does this happen every time?


Other information:
versions used :
perl-Glib-1.160-1mdv2008.0
perl-Gtk2-1.160-1mdv2008.0
perl-GStreamer-0.09-1mdv2007.0
libgstreamer0.10_0.10-0.10.14-1mdv2008.0
libglib2.0_0-2.14.1-2mdv2008.0


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