Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] avformat/mpegts: add option max_packet_size
Date: Sat, 5 Feb 2022 18:54:35 +0530
Message-ID: <18b01453-4956-0d2e-53b0-23f5d071341f@gyani.pro> (raw)
In-Reply-To: <7b3c913c-3066-f641-0815-75e72e8a3aec@gyani.pro>



On 2022-02-02 10:54 am, Gyan Doshi wrote:
>
>
> On 2022-02-02 12:42 am, James Almer wrote:
>>
>>
>> On 2/1/2022 3:47 PM, Michael Niedermayer wrote:
>>> On Sun, Jan 16, 2022 at 05:19:15AM +0000, Gyan Doshi wrote:
>>>> ffmpeg | branch: master | Gyan Doshi <ffmpeg@gyani.pro> | Wed Jan 
>>>> 12 20:57:59 2022 +0530| [bca30570d28bbaa07badadabf55ec3589201a82f] 
>>>> | committer: Gyan Doshi
>>>>
>>>> avformat/mpegts: add option max_packet_size
>>>>
>>>> Makes maximum size of emitted packet user-tunable.
>>>>
>>>> Default is existing 204800 bytes.
>>>>
>>>>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=bca30570d28bbaa07badadabf55ec3589201a82f 
>>>>>
>>>> ---
>>>>
>>>>   doc/demuxers.texi    |  4 ++++
>>>>   libavformat/mpegts.c | 11 ++++++-----
>>>>   2 files changed, 10 insertions(+), 5 deletions(-)
>>>
>>> Since this commit there is occasional memory corruption occuring
>>>
>>>    libavutil      57. 18.100 / 57. 18.100
>>>    libavcodec     59. 20.100 / 59. 20.100
>>>    libavformat    59. 17.101 / 59. 17.101
>>>    libavdevice    59.  5.100 / 59.  5.100
>>>    libavfilter     8. 25.100 /  8. 25.100
>>>    libswscale      6.  5.100 /  6.  5.100
>>>    libswresample   4.  4.100 /  4.  4.100
>>>    libpostproc    56.  4.100 / 56.  4.100
>>> invalid fastbin entry (free)
>>> doom/rtp-video: line 14: 15621 Aborted                 (core dumped) 
>>> ./ffmpeg_g -bitexact -protocol_whitelist http,tcp,rtp,udp -i 
>>> http://127.0.0.1:8080/test.sdp -bitexact -acodec mp2 -ab 64k -y -t 1 
>>> -threads 1 $TMP/out.avi
>>> Command exited with non-zero status 134
>>
>> Is the demuxer used in this scenario mpegts or mpegtsraw? The new 
>> option was added to the former but not the latter, yet if both read 
>> MpegTSContext.max_packet_size, for mpegtsraw it will always be 0.
>>
>> The option might need to be added to that demuxer too.
>
> The init appears to be via  avpriv_mpegts_parse_open in mpegts.c
>
> which has this note above,
>
>     /* parsing functions - called from other demuxers such as RTP */
>
> and in it, a few of the context fields are manually initialized. I 
> suspect hardcoding a value here may be enough.

Looks to be enough. Sent patch "avformat/mpegts: initialize 
max_packet_size when sub-demuxer"  to address this.

Regards,
Gyan
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

      reply	other threads:[~2022-02-05 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220116051916.342B441047A@natalya.videolan.org>
2022-02-01 18:47 ` Michael Niedermayer
2022-02-01 19:12   ` James Almer
2022-02-02  5:24     ` Gyan Doshi
2022-02-05 13:24       ` Gyan Doshi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18b01453-4956-0d2e-53b0-23f5d071341f@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git