[FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

[Kirithika Kalirathnam]

Hi All,

x265 v4.1 <https://bitbucket.org/multicoreware/x265_git/branch/master> is
released with the fixes addressing memory leak and other reported
issues.Please check it out.

*Thanks,*
*Kirithika*


On Mon, Nov 11, 2024 at 9:50 AM Kirithika Kalirathnam <
kirithika at multicorewareinc.com> wrote:

> Hi all,
>
> We would like to update that we have fixed the memory leaks and other
> issues reported in x265 and will be releasing v4.1 this week.
>
> *Thanks,*
> *Kirithika*
>
>
> On Fri, Oct 18, 2024 at 3:08 PM Kirithika Kalirathnam <
> kirithika at multicorewareinc.com> wrote:
>
>> Hi all ,
>>
>> We understand your concern behind marking x265 as experimental but we
>> wanted to let you know that our x265 development team is actively working
>> on resolving multiple issues that have been brought to our notice so far
>> through bitbucket issue tracker(including issue #482) and are planning to
>> release v4.1 with all the fixes shortly. We are also continuously levelling
>> up our tests to catch the issues beforehand and keep up code hygiene that
>> we have maintained so far. Hence we request this forum to reconsider the
>> decision for the benefit of several x265 users.
>>
>> *Thanks,*
>> *Kirithika*
>>
>>
>> On Thu, Oct 17, 2024 at 9:28 PM Zhao Zhili <quinkblack at foxmail.com>
>> wrote:
>>
>>>
>>> > 在 2024年10月17日，下午10:01，James Almer <jamrial at gmail.com> 写道：
>>> >
>>> > On 10/17/2024 10:49 AM, Timo Rothenpieler wrote:
>>> >>> On 17/10/2024 11:22, Anton Khirnov wrote:
>>> >>> Quoting Anton Khirnov (2023-03-15 15:45:25)
>>> >>>> This encoder leaks and overreads, as can be seen e.g. by running an
>>> >>>> encode under valgrind with default encoder parameters. This was
>>> known
>>> >>>> upstream since at least 2019 (e.g. bitbucket issue #482) but never
>>> fixed
>>> >>>> until now.
>>> >>>>
>>> >>>> Since upstream does not seem to practice basic code hygiene, make
>>> sure
>>> >>>> people do not use this encoder without knowing what they are getting
>>> >>>> into.
>>> >>>
>>> >>> Ping.
>>> >>>
>>> >>> I still think this should be applied. The issues seem to have gotten
>>> >>> worse, if anything, with recent ABI breakage.
>>> >> I would second this, without something drastic like this, no
>>> attention will be brought to the quite serious issues of that encoder.
>>> >
>>> > Ok.
>>>
>>> +1
>>>
>>> >
>>> > _______________________________________________
>>> > ffmpeg-devel mailing list
>>> > ffmpeg-devel at ffmpeg.org
>>> > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>>> >
>>> > To unsubscribe, visit link above, or email
>>> > ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>>> >
>>> > <OpenPGP_signature.asc>
>>>
>>> _______________________________________________
>>> ffmpeg-devel mailing list
>>> ffmpeg-devel at ffmpeg.org
>>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>>>
>>> To unsubscribe, visit link above, or email
>>> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>>>
>>