From: "\"zhilizhao(赵志立)\"" <quinkblack@foxmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avdevice/avfoundation: fix memleak Date: Sat, 19 Feb 2022 16:45:38 +0800 Message-ID: <tencent_EFC859F3E2137455CCE919EEBAA55C530B05@qq.com> (raw) In-Reply-To: <AM7PR03MB6660D8AE0A73DD4934FAE1D98F2D9@AM7PR03MB6660.eurprd03.prod.outlook.com> > On Feb 8, 2022, at 9:05 PM, Andreas Rheinhardt <andreas.rheinhardt@outlook.com> wrote: > > Thilo Borgmann: >> Am 08.02.22 um 13:50 schrieb Andreas Rheinhardt: >>> Thilo Borgmann: >>>> Am 04.02.22 um 17:19 schrieb Zhao Zhili: >>>>> --- >>>>> libavdevice/avfoundation.m | 10 ++++++---- >>>>> 1 file changed, 6 insertions(+), 4 deletions(-) >>>>> >>>>> diff --git a/libavdevice/avfoundation.m b/libavdevice/avfoundation.m >>>>> index 0cd6e646d5..2078c4879c 100644 >>>>> --- a/libavdevice/avfoundation.m >>>>> +++ b/libavdevice/avfoundation.m >>>>> @@ -106,6 +106,7 @@ typedef struct >>>>> int audio_device_index; >>>>> int audio_stream_index; >>>>> + char *url; >>>>> char *video_filename; >>>>> char *audio_filename; >>>>> @@ -299,6 +300,7 @@ static void destroy_context(AVFContext* ctx) >>>>> ctx->avf_delegate = NULL; >>>>> ctx->avf_audio_delegate = NULL; >>>>> + av_freep(&ctx->url); >>>>> av_freep(&ctx->audio_buffer); >>>> >>>> Why carry it in the context instead of adding the missing av_freep() in >>>> parse_device_name() ? >>>> >>> >>> Because video_filename and audio_filename point into it. >> >> Wondering if we couldn't skip av_strdup() and operate on s->url directly >> then. >> > > This would trash s->url. Ping. Can this patch set be applied? > > - Andreas > _______________________________________________ > 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:[~2022-02-19 8:45 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-04 16:19 Zhao Zhili 2022-02-08 12:47 ` Thilo Borgmann 2022-02-08 12:50 ` Andreas Rheinhardt 2022-02-08 13:03 ` Thilo Borgmann 2022-02-08 13:05 ` Andreas Rheinhardt 2022-02-19 8:45 ` "zhilizhao(赵志立)" [this message] 2022-02-22 12:12 ` Thilo Borgmann
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=tencent_EFC859F3E2137455CCE919EEBAA55C530B05@qq.com \ --to=quinkblack@foxmail.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