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 667568 - [0.11] [wma9] Segfaults when playing/discovering ASF file
[0.11] [wma9] Segfaults when playing/discovering ASF file
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-libav
0.11.x
Other Linux
: Normal blocker
: 0.11.x
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-01-09 15:08 UTC by Sebastian Dröge (slomo)
Modified: 2012-01-13 15:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastian Dröge (slomo) 2012-01-09 15:08:38 UTC
http://samples.mplayerhq.hu/A-codecs/WMA9/wmv-surroundtest_720p.wmv


Program received signal SIGSEGV, Segmentation fault.

Thread 140737269069568 (LWP 9055)

  • #0 put_bits
    at libavcodec/put_bits.h line 157
  • #1 ff_copy_bits
  • #2 save_bits
    at libavcodec/wmaprodec.c line 1456
  • #3 decode_packet
    at libavcodec/wmaprodec.c line 1530
  • #4 avcodec_decode_audio3
    at libavcodec/utils.c line 770
  • #5 gst_ffmpegdec_audio_frame
  • #6 gst_ffmpegdec_frame
  • #7 gst_ffmpegdec_chain
    at gstffmpegdec.c line 2808
  • #8 gst_pad_chain_data_unchecked
    at gstpad.c line 3306
  • #9 gst_pad_push_data
    at gstpad.c line 3509
  • #10 gst_single_queue_push_one
    at gstmultiqueue.c line 1056
  • #11 gst_multi_queue_loop
    at gstmultiqueue.c line 1287
  • #12 gst_task_func
    at gsttask.c line 322
  • #13 g_thread_pool_thread_proxy
    at /tmp/buildd/glib2.0-2.28.6/./glib/gthreadpool.c line 319
  • #14 g_thread_create_proxy
    at /tmp/buildd/glib2.0-2.28.6/./glib/gthread.c line 1897
  • #15 start_thread
    at pthread_create.c line 304
  • #16 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #17 ??

Comment 1 Mark Nauwelaerts 2012-01-13 15:03:06 UTC
Seems to have disappeared with bug #667567 being fixed.