On Sat, 2020-10-17 at 19:52 +0200, Andreas Rheinhardt wrote:
> Joakim Tjernlund:
> > On Fri, 2020-10-16 at 01:38 +0200, Andreas Rheinhardt wrote:
> > > CAUTION: This email originated from outside of the organization. Do not
> > > click links or open attachments unless you recognize the sender and
Joakim Tjernlund:
> On Fri, 2020-10-16 at 01:38 +0200, Andreas Rheinhardt wrote:
>> CAUTION: This email originated from outside of the organization. Do not
>> click links or open attachments unless you recognize the sender and know the
>> content is safe.
>>
>>
>> Joakim Tjernlund:
>>> From
>>>
On Fri, 2020-10-16 at 01:38 +0200, Andreas Rheinhardt wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> Joakim Tjernlund:
> > From
> > https://nam11.safelinks.
Joakim Tjernlund:
> From https://bugs.chromium.org/p/chromium/issues/detail?id=1095962
>
> This seems to be caused by the custom handling of "av_max_alloc(0)" in
> Chromium's ffmpeg fork to mean unlimited (added in [1]).
>
> Upstream ffmpeg doesn't treat 0 as a special
