We may not be able to do anything here (I'm not familiar with Teams), but good to have a bug for tracking purposes anyway.
FWIW I've been using teams 13653 and just now 26453 +system-ffmpeg with ffmpeg-4.4-r1[chromium] and works for me.
(In reply to Geoff Leach from comment #1) > FWIW I've been using teams 13653 and just now 26453 +system-ffmpeg with > ffmpeg-4.4-r1[chromium] and works for me. Nice, that would mean that the need for this ffmpeg patch is gone: --- ./libavutil/mem.c.org 2020-10-07 19:22:30.286728200 +0200 +++ ./libavutil/mem.c 2020-10-07 19:24:04.039885660 +0200 @@ -71,6 +71,8 @@ static size_t max_alloc_size= INT_MAX; void av_max_alloc(size_t max){ + if (!max) + max = INT_MAX; /* be compatible to older < 4.3 versions */ max_alloc_size = max; } which our Teams has been using for a long time now(and +system-ffmpeg)
teams-1.5.00.10453[system-ffmpeg] with ffmpeg-4.4.1-r5 and the above patch works fine for me.
teams-1.5.00.10453[swiftshader system-ffmpeg] and ffmpeg-4.4.2 works for me, albeit limited testing, watching a seminar, so only down no up. Based on [seden] ebuild. nvidia-drivers-515.48.07. The ffmpeg patch is gone, not mentioned in the ebuild.
Sam's given us a newer <ffmpeg-4.3 that should fix the security bugs this previously blocked! commit 31baf58256ca04e305510ce86df9f6d83948f853 Author: Sam James <sam@gentoo.org> Date: Sat Sep 3 06:24:50 2022 +0100 media-video/ffmpeg: add 4.2.7 Fixes a bunch of CVEs that we've had fixed in newer versions for a while, but until we can clean up 4.2.x, we may as well bump to the latest in that series... Bug: https://bugs.gentoo.org/842267 Bug: https://bugs.gentoo.org/795696 Bug: https://bugs.gentoo.org/781146 Signed-off-by: Sam James <sam@gentoo.org>
