[gstreamer-bugs] [Bug 562086] mpeg2 stream crashes something in gstreamer

[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=562086

  GStreamer | don't know | Ver: HEAD CVS




------- Comment #4 from Tom Parker  2008-11-24 22:03 UTC -------
Created an attachment (id=123346)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=123346&action=view)
Valgrind log

Just ran this through Valgrind. Full log is attached, but here's the first
error (using libmpeg2-4 version 0.5.1-1): 

Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
==17621== Thread 2:
==17621== Invalid write of size 8
==17621==    at 0x703B668: mpeg2_idct_copy_sse2 (in /usr/lib/libmpeg2.so.0.1.0)
==17621==  Address 0x8b7f170 is 691,208 bytes inside a block of size 691,215
alloc'd
==17621==    at 0x4023D6E: malloc (vg_replace_malloc.c:207)
==17621==    by 0x416D973: g_malloc (gmem.c:131)
==17621==    by 0x405F46B: gst_buffer_new_and_alloc (gstbuffer.c:328)
==17621==    by 0x701256A: gst_mpeg2dec_chain (gstmpeg2dec.c:474)
==17621==    by 0x4085E88: gst_pad_chain_unchecked (gstpad.c:3877)
==17621==    by 0x40870C9: gst_pad_push (gstpad.c:4045)
==17621==    by 0x4AB8BF7: stop_typefinding (gsttypefindelement.c:476)
==17621==    by 0x4AB9678: gst_type_find_element_chain
(gsttypefindelement.c:692)
==17621==    by 0x4085E88: gst_pad_chain_unchecked (gstpad.c:3877)
==17621==    by 0x40870C9: gst_pad_push (gstpad.c:4045)
==17621==    by 0x4077CA9: gst_proxy_pad_do_chain (gstghostpad.c:207)
==17621==    by 0x4085E88: gst_pad_chain_unchecked (gstpad.c:3877)


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