From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avfillter/buffersrc: activate and EOF fix Date: Wed, 1 Nov 2023 11:23:44 -0300 Message-ID: <d0bd936e-3f39-4773-8b89-9769e5a7c2ce@gmail.com> (raw) In-Reply-To: <ZUJZKAWtxdmbp2zt@phare.normalesup.org> On 11/1/2023 10:56 AM, Nicolas George wrote: > Jan Ekström (12023-11-01): >> So my question is: Does this test case not improve for you after you >> have applied these patches? Or are you speaking of a separate problem >> which is bad both in master as well as after these patches have been >> applied? > > This is the test case Paul posted yesterday (except you had the > politeness to de-script it) and I used to see that it does not fix the > issue. 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? > > Anyway, except in the simplest of cases, if a change does not include an > analysis of why the problem happens and how the change prevents it from > happening the simplest way, then it is not a bug fix, it is just dumb > luck. And most likely, the bug is not really gone, it just shifted to > not be triggered by the test case. > > There is no such analysis in Paul's patches. If he can submit such an > analysis these patches can move forward. But based on my knowledge of > the activate code (I wrote it…) I am pretty certain this kind of bug > does not need a source with a single output to be switched to activate. > > Regards, > > > _______________________________________________ > 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". _______________________________________________ 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".
next prev parent reply other threads:[~2023-11-01 14:23 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-27 12:38 Paul B Mahol 2023-10-27 12:53 ` Nicolas George 2023-10-27 13:07 ` Paul B Mahol 2023-10-27 13:02 ` Nicolas George 2023-10-27 13:18 ` Paul B Mahol 2023-10-27 17:51 ` Paul B Mahol 2023-10-27 17:54 ` Nicolas George 2023-10-27 22:48 ` Paul B Mahol 2023-10-29 9:38 ` Nicolas George 2023-10-29 21:46 ` Paul B Mahol 2023-10-31 10:55 ` Nicolas George 2023-10-31 20:13 ` Paul B Mahol 2023-10-31 20:14 ` Paul B Mahol 2023-11-01 13:58 ` Nicolas George 2023-11-01 14:15 ` Paul B Mahol 2023-11-01 14:13 ` Nicolas George 2023-11-02 9:56 ` Paul B Mahol 2023-11-02 9:50 ` Nicolas George 2023-11-02 10:00 ` Paul B Mahol 2023-11-02 10:03 ` Nicolas George 2023-11-02 10:18 ` Paul B Mahol 2023-11-02 10:15 ` Nicolas George 2023-11-02 20:05 ` Tristan Matthews 2023-11-03 19:04 ` Nicolas George 2023-11-03 20:47 ` Paul B Mahol 2023-11-04 19:05 ` Nicolas George 2023-11-01 13:48 ` Jan Ekström 2023-11-01 13:56 ` Nicolas George 2023-11-01 14:23 ` James Almer [this message] 2023-11-01 14:28 ` Nicolas George
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=d0bd936e-3f39-4773-8b89-9769e5a7c2ce@gmail.com \ --to=jamrial@gmail.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