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 680494 - [0.11] faad: gst_buffer_unmap: assertion `GST_IS_BUFFER (buffer)' failed on push mode seeking
[0.11] faad: gst_buffer_unmap: assertion `GST_IS_BUFFER (buffer)' failed on p...
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
0.11.x
Other Linux
: Normal critical
: 0.11.x
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-07-23 22:38 UTC by Tim-Philipp Müller
Modified: 2012-08-02 14:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tim-Philipp Müller 2012-07-23 22:38:33 UTC 
tpm@zingle:~/gst/0.11/gst-plugins-base/tests/examples/playback$ G_DEBUG=fatal_warnings gdb --args ./.libs/lt-playback-test 0 'http://video.blendertestbuilds.de/download.blender.org/peach/trailer_480p.mov'


message from "videosink-actual-sink-xvimage" (tag): GstMessageTag, taglist=(taglist)"taglist\,\ maximum-bitrate\=\(uint\)25771000\;";
message from "source" (error): GstMessageError, gerror=(GError)NULL, debug=(string)"gstsouphttpsrc.c\(806\):\ gst_soup_http_src_got_headers_cb\ \(\):\ /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0/GstSoupHTTPSrc:source:\012Server\ does\ not\ accept\ Range\ HTTP\ header\,\ URL:\ http://video.blendertestbuilds.de/download.blender.org/peach/trailer_480p.mov";
Buffering, setting pipeline to PAUSED ...

(lt-playback-test:26456): GStreamer-CRITICAL **: gst_buffer_unmap: assertion `GST_IS_BUFFER (buffer)' failed

Program received signal SIGTRAP, Trace/breakpoint trap.

+ Trace 230568

Thread 140736961185536 (LWP 26512)

  • #0 g_logv
    at /tmp/buildd/glib2.0-2.32.3/./glib/gmessages.h line 101
  • #1 g_log
    at /tmp/buildd/glib2.0-2.32.3/./glib/gmessages.c line 792
  • #2 gst_faad_handle_frame
    at gstfaad.c line 804
  • #3 gst_audio_decoder_handle_frame
    at gstaudiodecoder.c line 1088
  • #4 gst_audio_decoder_push_buffers
    at gstaudiodecoder.c line 1184
  • #5 gst_audio_decoder_chain_forward
    at gstaudiodecoder.c line 1287
  • #6 gst_audio_decoder_chain
    at gstaudiodecoder.c line 1536
  • #7 gst_pad_chain_data_unchecked
    at gstpad.c line 3587
  • #8 gst_pad_push_data
    at gstpad.c line 3800
  • #9 gst_pad_push
    at gstpad.c line 3903
  • #10 gst_base_parse_push_frame
    at gstbaseparse.c line 2074
  • #11 gst_base_parse_chain
    at gstbaseparse.c line 2533
  • #12 gst_pad_chain_data_unchecked
    at gstpad.c line 3587
  • #13 gst_pad_push_data
    at gstpad.c line 3800
  • #14 gst_pad_push
    at gstpad.c line 3903
  • #15 gst_single_queue_push_one
    at gstmultiqueue.c line 1057
  • #16 gst_multi_queue_loop
    at gstmultiqueue.c line 1303
  • #17 gst_task_func
    at gsttask.c line 316
  • #18 g_thread_pool_thread_proxy
    at /tmp/buildd/glib2.0-2.32.3/./glib/gthreadpool.c line 309
  • #19 g_thread_proxy
    at /tmp/buildd/glib2.0-2.32.3/./glib/gthread.c line 801
  • #20 start_thread
    at pthread_create.c line 304
  • #21 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #22 ?? 






Comment 1


Mark Nauwelaerts





          2012-07-24 09:51:33 UTC
        



This does not happen with pushfile:// variant, and fiddling a bit in faad can avoid the assertion failure, but then there are lots of decoding errors and things end that way.

So all in all it looks like something going wrong/corrupt in the download buffering (whether or not due to the unsupported HTTP Range).






Comment 2


Mark Nauwelaerts





          2012-08-02 14:19:28 UTC
        



Oops, looks like the fiddling in faad mentioned above is really needed and is also the real problem after all:

commit 19ca77e95eaa4745cb9b6f64edee5d03b2334452
Author: Mark Nauwelaerts <mark.nauwelaerts@collabora.co.uk>
Date:   Thu Aug 2 14:40:55 2012 +0200

    faad: do not access frame buffer following _finish_frame call
    
    Fixes https://bugzilla.gnome.org/show_bug.cgi?id=680494