From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 0599C47B06 for ; Wed, 1 Nov 2023 14:29:05 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 9DC1668CDA6; Wed, 1 Nov 2023 16:29:01 +0200 (EET) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id E0DCD68CD1F for ; Wed, 1 Nov 2023 16:28:54 +0200 (EET) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 3A1ESseU004464 for ; Wed, 1 Nov 2023 15:28:54 +0100 Received: by phare.normalesup.org (Postfix, from userid 1001) id 17236E6C30; Wed, 1 Nov 2023 15:28:54 +0100 (CET) Date: Wed, 1 Nov 2023 15:28:54 +0100 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: MIME-Version: 1.0 In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Wed, 01 Nov 2023 15:28:54 +0100 (CET) Subject: Re: [FFmpeg-devel] [PATCH] avfillter/buffersrc: activate and EOF fix X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============9005464399241492788==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============9005464399241492788== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ReAmIHSVl+fMznft" Content-Disposition: inline --ReAmIHSVl+fMznft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable James Almer (12023-11-01): > Can you be more specific? Do you not see the result Jan described? Do you > see something different? Or is it that you do see what he described, but > it's not a proper fix in your opinion as Paul's patch simply prevents the > leak from being triggered in his specific testcase? I posted my console output in the last mail. And even if it did make the bug go away, such an important change is not acceptable without the proof that it is necessary in the commit message. Regards, --=20 Nicolas George --ReAmIHSVl+fMznft Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmVCYKQACgkQcZVLI8pN xgxFdQ//XTJBLKwFWj1GABuWTVJn6JMnk95an0FZuncPdBdGXKbcbft8AgLcRdrg 48R+915RIuWP0GHEM5CnPmobVPQm+914v606VZM18Cl0DQqax8si3ks4Zy50wq6n 1++TPXynZFWwhPwUmktQlP2PTL18YuIJis4mwv6r/G3LRU+T0DmjYMcMMoS2onC8 xAO/O9J5x8kL4qr/sRAsnpCgj//QdfnwTxfXOF18uiaIEp9jCFm6kzMr2IqbXpOD 1GbeZCQXPu/WRr4AR/2FNG0iGWPMN78dA/TA0EyVHi2eD208mKlaBw74dHcFP9ue Gl74/k2qoGzXDqd2o4f9oPxtvbJCWcsKQ5fGgJuyLyCsKqknu1+xUh77LhSMxrna R2H4PZB+92pu+TcmI6CNNS1x83uuU3RvWkuHMtlALQoi9bvj9pJoXoiB5uT2Kn6J Xx5TgOkx4JfaNDQKfcacNP9eJvjeKSOAV62tdD+D5lFbDqayM+0dND3d7DSZTAT0 3L763zN1ysEzhfpUXKwrcuwj1xxxVwBIrUu9ZlMLK7LvAlJrBMNAmrU4dNZNZrie xiGVp1Y0RVa2X/3Rcto8a0yn596HdP1C4Q/Nc5R5YVGtgZQaTaR9kO67GBMaDdRb G3s1cE8d6LMJazTPYijqeY5LlKYDloiWh6o61A7ZelTuaTGDi08= =Bv6R -----END PGP SIGNATURE----- --ReAmIHSVl+fMznft-- --===============9005464399241492788== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============9005464399241492788==--