Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/libx265: Don't copy A53 closed captions by default
Date: Tue, 11 Jun 2024 10:05:54 +0200
Message-ID: <GV1P250MB073780FE5472D0DA0CC78A598FC72@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <501e38d3c8a0ebbdf518ccef459cc17fd97ed589.camel@haerdin.se>

Tomas Härdin:
> tis 2024-06-11 klockan 09:42 +0200 skrev Andreas Rheinhardt:
>> The SEI handling of libx265 is buggy and can easily lead
>> to memory corruption: It reuses certain buffers, but when
>> reusing them it presumes that it is enough for these buffers
>> to exist and does not check whether they are actually large
>> enough to hold what is intended to be stored in them.*
>>
>> Our users are exposed to this because forwarding A53 CC data
>> is enabled by default. Change this to make it disabled
>> by default.
>>
>> "Fixes" tickets #9666, #10411, #11052 and (presumably) #10906.
> 
> Shouldn't users use non-buggy versions of libx26? I've had people ask
> about CC, and I'm sure many users would be annoyed at them suddenly
> breaking. I suggest complaining loudly at compile time and/or when
> loading libx265 instead

Non-buggy versions of libx265? People use what they have because it exists.

- Andreas

_______________________________________________
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:[~2024-06-11  8:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  7:42 Andreas Rheinhardt
2024-06-11  8:04 ` Tomas Härdin
2024-06-11  8:05   ` Andreas Rheinhardt [this message]
2024-06-11  8:13     ` Tomas Härdin
2024-06-11  8:16       ` Andreas Rheinhardt
2024-06-11  8:22         ` Tomas Härdin
2024-06-13  4:40 ` Andreas Rheinhardt

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=GV1P250MB073780FE5472D0DA0CC78A598FC72@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
    --to=andreas.rheinhardt@outlook.com \
    --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