From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] fftools/cmdutils: Add av_freep() to avoid memory leak Date: Sat, 12 Jul 2025 01:20:15 +0200 Message-ID: <20250711232015.GW29660@pb2> (raw) In-Reply-To: <20250710194149.27218-1-jiashengjiangcool@gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1308 bytes --] On Thu, Jul 10, 2025 at 07:41:49PM +0000, Jiasheng Jiang wrote: > Add av_freep() to free new_elem to avoid memory leak. > > Fixes: 2d0bfbd0fa ("fftools/cmdutils: Use av_dynarray_add_nofree()") > Signed-off-by: Jiasheng Jiang <jiashengjiangcool@gmail.com> > --- > fftools/cmdutils.c | 8 ++++++-- > 1 file changed, 6 insertions(+), 2 deletions(-) > > diff --git a/fftools/cmdutils.c b/fftools/cmdutils.c > index e442935cae..5c8d09f87a 100644 > --- a/fftools/cmdutils.c > +++ b/fftools/cmdutils.c > @@ -1471,9 +1471,13 @@ void *allocate_array_elem(void *ptr, size_t elem_size, int *nb_elems) > { > void *new_elem; > > - if (!(new_elem = av_mallocz(elem_size)) || > - av_dynarray_add_nofree(ptr, nb_elems, new_elem) < 0) > + new_elem = av_mallocz(elem_size); > + if (!new_elem) > return NULL; > + if (av_dynarray_add_nofree(ptr, nb_elems, new_elem) < 0) { > + av_freep(&new_elem); > + return NULL; > + } > return new_elem; teh return NULL is not needed as av_freep sets new_elem to NULL [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety -- Benjamin Franklin [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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".
prev parent reply other threads:[~2025-07-11 23:20 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-10 19:41 Jiasheng Jiang 2025-07-11 23:20 ` Michael Niedermayer [this message]
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=20250711232015.GW29660@pb2 \ --to=michael@niedermayer.cc \ --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