[Bug 792825] rtph264pay: add support for STAP-A bundling

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=792825

--- Comment #8 from Dirk-Jan C. Binnema <djcb at djcbsoftware.nl> ---
With master (and with the patch) I see two cases of 'definitely lost' (see
below), but they are in the _de_payloader, rather than the payloader.

Running suite(s): rtp_data_test
==11909== 279 (72 direct, 207 indirect) bytes in 1 blocks are definitely lost
in loss record 2,111 of 2,156
==11909==    at 0x4C2DBAB: malloc (vg_replace_malloc.c:299)
==11909==    by 0x6B9A2B5: g_malloc (gmem.c:99)
==11909==    by 0x6BB1E46: g_slice_alloc (gslice.c:1025)
==11909==    by 0x5C5CD3A: gst_caps_new_empty (gstcaps.c:253)
==11909==    by 0x5C5CF18: gst_caps_new_simple (gstcaps.c:326)
==11909==    by 0x84DFD8D: gst_rtp_h264_set_src_caps (gstrtph264depay.c:324)
==11909==    by 0x84E1873: gst_rtp_h264_depay_setcaps (gstrtph264depay.c:738)
==11909==    by 0x875E83C: gst_rtp_base_depayload_setcaps
(gstrtpbasedepayload.c:289)
==11909==    by 0x875E83C: gst_rtp_base_depayload_handle_event
(gstrtpbasedepayload.c:571)
==11909==    by 0x5C8C136: gst_pad_send_event_unchecked (gstpad.c:5756)
==11909==    by 0x5C8C62F: gst_pad_push_event_unchecked (gstpad.c:5409)
==11909==    by 0x5C8CAD5: push_sticky (gstpad.c:3932)
==11909==    by 0x5C8A6E7: events_foreach (gstpad.c:612)
==11909==    by 0x5C959E6: check_sticky (gstpad.c:3992)
==11909==    by 0x5C959E6: gst_pad_push_event (gstpad.c:5543)
==11909==    by 0x875CD52: gst_pad_set_caps (gstcompat.h:59)
==11909==    by 0x875CD52: gst_rtp_base_payload_negotiate
(gstrtpbasepayload.c:1057)
==11909==    by 0x875D427: gst_rtp_base_payload_chain (gstrtpbasepayload.c:627)
==11909==    by 0x5C8E031: gst_pad_chain_data_unchecked (gstpad.c:4334)
==11909==    by 0x5C8E031: gst_pad_push_data (gstpad.c:4590)
==11909==    by 0x5C94A01: gst_pad_push (gstpad.c:4709)
==11909==    by 0x5C7B45A: gst_proxy_pad_chain_default (gstghostpad.c:127)
==11909==    by 0x5C8E031: gst_pad_chain_data_unchecked (gstpad.c:4334)
==11909==    by 0x5C8E031: gst_pad_push_data (gstpad.c:4590)
==11909==    by 0x5C94A01: gst_pad_push (gstpad.c:4709)
==11909== 
==12298== 9,488 (816 direct, 8,672 indirect) bytes in 3 blocks are definitely
lost in loss record 2,653 of 2,658
==12298==    at 0x4C2DBAB: malloc (vg_replace_malloc.c:299)
==12298==    by 0x6B9A2B5: g_malloc (gmem.c:99)
==12298==    by 0x6BB1E46: g_slice_alloc (gslice.c:1025)
==12298==    by 0x5C53A4A: gst_buffer_new (gstbuffer.c:801)
==12298==    by 0x5C557B4: gst_buffer_copy_with_flags (gstbuffer.c:662)
==12298==    by 0x5C88477: gst_mini_object_make_writable (gstminiobject.c:315)
==12298==    by 0x9049288: set_headers (gstrtpbasedepayload.c:716)
==12298==    by 0x9049C6E: gst_rtp_base_depayload_prepare_push
(gstrtpbasedepayload.c:754)
==12298==    by 0x904A218: gst_rtp_base_depayload_push
(gstrtpbasedepayload.c:785)
==12298==    by 0x8DF4C35: gst_rtp_vorbis_depay_switch_codebook
(gstrtpvorbisdepay.c:436)
==12298==    by 0x8DF4C35: gst_rtp_vorbis_depay_process
(gstrtpvorbisdepay.c:513)
==12298==    by 0x904A624: gst_rtp_base_depayload_handle_buffer.isra.3
(gstrtpbasedepayload.c:429)
==12298==    by 0x5C8E031: gst_pad_chain_data_unchecked (gstpad.c:4334)
==12298==    by 0x5C8E031: gst_pad_push_data (gstpad.c:4590)
==12298==    by 0x5C94A01: gst_pad_push (gstpad.c:4709)
==12298==    by 0x8DF58EF: gst_rtp_vorbis_pay_flush_packet
(gstrtpvorbispay.c:341)
==12298==    by 0x8DF5E33: gst_rtp_vorbis_pay_payload_buffer
(gstrtpvorbispay.c:635)
==12298==    by 0x8DF6FA9: gst_rtp_vorbis_pay_handle_buffer
(gstrtpvorbispay.c:876)
==12298==    by 0x5C8E031: gst_pad_chain_data_unchecked (gstpad.c:4334)
==12298==    by 0x5C8E031: gst_pad_push_data (gstpad.c:4590)
==12298==    by 0x5C94A01: gst_pad_push (gstpad.c:4709)
==12298==    by 0x4E73B2B: gst_audio_encoder_finish_frame
(gstaudioencoder.c:991)
==12298==    by 0x84BE335: gst_vorbis_enc_output_buffers (gstvorbisenc.c:992)
==12298== 
100%: Checks: 49, Failures: 0, Errors: 0
Check suite rtp_payloading ran in 79.662s (tests failed: 0)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.