[Bug 688824] theoradec: crash in theora_handle_type_packet()

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=688824
  GStreamer | gst-plugins-base | 1.x

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO

--- Comment #5 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2013-01-05 18:57:14 UTC ---
Do you have a test case that does not involve rygel?

Or maybe a valgrind run that does not have this in it:

==4104== Invalid write of size 4
==4104==    at 0x5FC8EFC: g_main_context_dispatch (gmain.c:2668)
==4104==    by 0x5FC92EF: g_main_context_iterate.isra.25 (gmain.c:3290)
==4104==    by 0x5FC96E9: g_main_loop_run (gmain.c:3484)
==4104==    by 0x405E8C: rygel_main_run (rygel-main.vala:81)
==4104==    by 0x40857C: rygel_main_main (rygel-main.vala:290)
==4104==    by 0x4086AD: main (rygel-main.vala:263)
==4104==  Address 0xed7a35c is 44 bytes inside a block of size 96 free'd
==4104==    at 0x4C2A82E: free (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4104==    by 0x5FC6973: g_source_unref_internal (gmain.c:1839)
==4104==    by 0x6D0BDC0: soup_message_io_stop (soup-message-io.c:144)
==4104==    by 0x6D0BE13: soup_message_io_cleanup (soup-message-io.c:100)
==4104==    by 0x6D0C066: soup_message_io_finished (soup-message-io.c:163)
==4104==    by 0x6D0D4EF: io_run (soup-message-io.c:911)
==4104==    by 0x5FC8FA2: g_main_context_dispatch (gmain.c:2715)
==4104==    by 0x5FC92EF: g_main_context_iterate.isra.25 (gmain.c:3290)
==4104==    by 0x5FC96E9: g_main_loop_run (gmain.c:3484)
==4104==    by 0x405E8C: rygel_main_run (rygel-main.vala:81)
==4104==    by 0x40857C: rygel_main_main (rygel-main.vala:290)
==4104==    by 0x4086AD: main (rygel-main.vala:263)


Can you reproduce it with gst-launch-1.0 somehow?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.