From: Marton Balint <cus@passwd.hu> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] SW's Patchsets Overview Date: Wed, 2 Apr 2025 21:45:16 +0200 (CEST) Message-ID: <c45a5869-e39e-bc20-0559-079f0b93ca37@passwd.hu> (raw) In-Reply-To: <DM8P223MB0365066DF0B56E60A0E2C4E9BAAF2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> On Wed, 2 Apr 2025, softworkz . wrote: > Hello everybody, > > with freshly gained push access rights, I want to act responsibly and > carefully, and also avoid unexpected surprises so I'm not going to rush > things. Due to that change, I thought it might be good to post an > overview of the patchsets I am intending to push in the near future: Thanks for the heads up. [...] > avutil/log: Replace addresses in log output with simple ids > > GitHub: https://github.com/ffstaging/FFmpeg/pull/59 > Patchwork: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14094 To be honest, I don't like this at all. You duplicate a lot of code from avutil/log, and the implementation has quite a few problems, some of them not really fixable. - creating object IDs in the order the objects log something (what if they do not? What if it depends on loglevel?) - tracking object IDs based on their address - objects are allocated and removed at runtime, it is possible that an address will be re-used for a different object later on - linear search of addresses. A long ffmpeg process can constantly create objects during runtime, eventually completely depleting the pool and causing an extensive search for all future logs. So overall I don't think it's worth pursuing this, especially since most users won't care neither about the ID, nor about the address... Regards, Marton _______________________________________________ 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:[~2025-04-02 19:43 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-04-02 1:07 softworkz . 2025-04-02 19:45 ` Marton Balint [this message] 2025-04-02 20:18 ` softworkz . 2025-04-06 21:04 ` Marton Balint 2025-04-06 21:12 ` softworkz . 2025-04-08 22:24 ` Michael Niedermayer 2025-04-08 22:45 ` softworkz . 2025-04-07 9:14 ` Nicolas George 2025-04-07 9:47 ` softworkz . 2025-04-08 22:53 ` Marton Balint 2025-04-08 23:31 ` softworkz . 2025-04-09 8:33 ` 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=c45a5869-e39e-bc20-0559-079f0b93ca37@passwd.hu \ --to=cus@passwd.hu \ --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