From: Alexander Strasser via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Alexander Strasser <eclipse7@gmx.net>
Subject: Re: [FFmpeg-devel] [PATCH] examples: Replace with proper error handling to avoid potential memory errors
Date: Wed, 6 Aug 2025 10:11:51 +0200
Message-ID: <aJMOR3svxw0bH2V6@metallschleim.local> (raw)
In-Reply-To: <aJJnDPBLpORYY3Jk@phare.normalesup.org>
On 2025-08-05 22:18 +0200, Nicolas George wrote:
> Jiasheng Jiang (HE12025-08-05):
> > Moreover, replace with proper error handling to avoid potential memory leak.
>
> There is no potential memory leak with exit().
>
> And it does not have to be a lesson in good C practices.
I'm a bit undecided about this; especially because these are example files.
Best would be to have them correct, small, and beautiful while still
promoting good C practices.
I agree that the patch as proposed is not an improvement over all.
I would say it would be best to shorten it to only the first change:
--- a/doc/examples/decode_audio.c
+++ b/doc/examples/decode_audio.c
@@ -128,41 +128,48 @@ int main(int argc, char **argv)
outfilename = argv[2];
pkt = av_packet_alloc();
+ if (!pkt)
+ exit(1);
If someone wants to improve the example files to better handle errors
and resource de-allocation for real world use cases, then it should be
a follow up submission.
Best regards,
Alexander
_______________________________________________
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-08-06 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 18:56 Jiasheng Jiang
2025-08-05 20:18 ` Nicolas George
2025-08-06 8:11 ` Alexander Strasser via ffmpeg-devel [this message]
2025-08-06 9:14 ` 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=aJMOR3svxw0bH2V6@metallschleim.local \
--to=ffmpeg-devel@ffmpeg.org \
--cc=eclipse7@gmx.net \
/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