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 423362 - SIGSEGV trying to play MMS stream
SIGSEGV trying to play MMS stream
Status: RESOLVED DUPLICATE of bug 347151
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
0.10.12
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-27 15:23 UTC by Sven Arvidsson
Modified: 2007-03-27 21:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Sven Arvidsson 2007-03-27 15:23:49 UTC
Trying to play back this MMS stream, mms://media.lightreading.com/drtv/2006/11/111687_01_256K.wmv results in a GStreamer SIGSEGV. "Caught SIGSEGV accessing address 0xc". 

This stream plays without problems in MPlayer.

I was trying to watch the video segments from this article in Totem.
http://www.darkreading.com/document.asp?doc_id=120172&WT.svl=news1_2

Using,
gstreamer0.10-ffmpeg                     0.10.2-1
gstreamer0.10-gnomevfs                   0.10.12-1
gstreamer0.10-plugins-base               0.10.12-1
gstreamer0.10-plugins-good               0.10.5-4
gstreamer0.10-plugins-really-bad         0.10.3-0.5
gstreamer0.10-plugins-ugly               0.10.5-1
gstreamer0.10-x                          0.10.12-1
libgstreamer0.10-0                       0.10.12-2
Comment 1 Tim-Philipp Müller 2007-03-27 20:52:22 UTC
Ouch, I get that too. I even get problems when just downloading the file with

  gst-launch mmssrc uri=mms://... ! filesink location=foo

(although only at the end).

Valgrind has this to say (this is with libmms debugging output enabled):

...
stream id 31
...
==2377== Invalid write of size 4
==2377==    at 0x468AC4A: interp_asf_header (mms.c:803)
==2377==    by 0x468BAFD: mms_connect (mms.c:1232)
==2377==    by 0x4685BD7: gst_mms_start (gstmms.c:290)
==2377==    by 0x46A156B: gst_base_src_start (gstbasesrc.c:1823)
==2377==    by 0x46A27D1: gst_base_src_activate_push (gstbasesrc.c:1958)
==2377==    by 0x406EC1E: gst_pad_activate_push (gstpad.c:886)
==2377==    by 0x406F104: gst_pad_activate_default (gstpad.c:559)
==2377==    by 0x406F1CB: gst_pad_set_active (gstpad.c:648)
==2377==    by 0x405699A: activate_pads (gstelement.c:2423)
==2377==    by 0x40629F6: gst_iterator_fold (gstiterator.c:503)
==2377==    by 0x4056411: iterator_activate_fold_with_resync (gstelement.c:2455)
==2377==    by 0x40564AD: gst_element_pads_activate (gstelement.c:2490)
==2377==  Address 0x49B19A4 is 4 bytes after a block of size 113,208 alloc'd
==2377==    at 0x4021396: malloc (vg_replace_malloc.c:149)
==2377==    by 0x468B341: mms_connect (mms.c:1044)
==2377==    by 0x4685BD7: gst_mms_start (gstmms.c:290)
==2377==    by 0x46A156B: gst_base_src_start (gstbasesrc.c:1823)
==2377==    by 0x46A27D1: gst_base_src_activate_push (gstbasesrc.c:1958)
==2377==    by 0x406EC1E: gst_pad_activate_push (gstpad.c:886)
==2377==    by 0x406F104: gst_pad_activate_default (gstpad.c:559)
==2377==    by 0x406F1CB: gst_pad_set_active (gstpad.c:648)
==2377==    by 0x405699A: activate_pads (gstelement.c:2423)
==2377==    by 0x40629F6: gst_iterator_fold (gstiterator.c:503)
==2377==    by 0x4056411: iterator_activate_fold_with_resync (gstelement.c:2455)
==2377==    by 0x40564AD: gst_element_pads_activate (gstelement.c:2490)
...
stream id 31, bitrate 191498

There is a patch for this here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1521441&group_id=101989&atid=630609

But libmms is effectively unmaintained, so you need to push your distro to include this fix.



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 347151 ***
Comment 2 Sven Arvidsson 2007-03-27 21:31:58 UTC
Works great after applying the patch, thank you for the explanation and the link to the patch!