From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 2/3] avcodec/avcodec: don't free coded_side_data in ff_codec_close() when decoding Date: Wed, 1 May 2024 17:51:22 -0300 Message-ID: <01946ed3-ef94-4bb3-91e9-cbcc81c25fcc@gmail.com> (raw) In-Reply-To: <AS8P250MB074481334C93D6FE949EF7188F192@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> On 5/1/2024 5:40 PM, Andreas Rheinhardt wrote: > James Almer: >> It's a user-set parameter shared with AVCodecParameters, so it should only >> be freed by avcodec_free_context(). >> >> Signed-off-by: James Almer <jamrial@gmail.com> >> --- >> libavcodec/avcodec.c | 11 ++++++----- >> libavcodec/options.c | 4 ++++ >> 2 files changed, 10 insertions(+), 5 deletions(-) >> >> diff --git a/libavcodec/avcodec.c b/libavcodec/avcodec.c >> index fc8a40e4db..e560efff6a 100644 >> --- a/libavcodec/avcodec.c >> +++ b/libavcodec/avcodec.c >> @@ -458,11 +458,12 @@ av_cold void ff_codec_close(AVCodecContext *avctx) >> >> av_freep(&avctx->internal); >> } >> - >> - for (i = 0; i < avctx->nb_coded_side_data; i++) >> - av_freep(&avctx->coded_side_data[i].data); >> - av_freep(&avctx->coded_side_data); >> - avctx->nb_coded_side_data = 0; >> + if (av_codec_is_encoder(avctx->codec)) { >> + for (i = 0; i < avctx->nb_coded_side_data; i++) >> + av_freep(&avctx->coded_side_data[i].data); >> + av_freep(&avctx->coded_side_data); >> + avctx->nb_coded_side_data = 0; >> + } >> >> av_buffer_unref(&avctx->hw_frames_ctx); >> av_buffer_unref(&avctx->hw_device_ctx); >> diff --git a/libavcodec/options.c b/libavcodec/options.c >> index 0c3b40a186..7c32a71275 100644 >> --- a/libavcodec/options.c >> +++ b/libavcodec/options.c >> @@ -177,6 +177,10 @@ void avcodec_free_context(AVCodecContext **pavctx) >> av_freep(&avctx->inter_matrix); >> av_freep(&avctx->rc_override); >> av_channel_layout_uninit(&avctx->ch_layout); >> + for (int i = 0; i < avctx->nb_coded_side_data; i++) >> + av_freep(&avctx->coded_side_data[i].data); >> + av_freep(&avctx->coded_side_data); >> + avctx->nb_coded_side_data = 0; >> av_frame_side_data_free( >> &avctx->decoded_side_data, &avctx->nb_decoded_side_data); >> > > 1. ff_codec_close() already has an "if is_encoder" branch, it does not > need another one. > 2. The code in ff_codec_close() will be redundant as soon as > FF_API_AVCODEC_CLOSE is no more, so it should be inside > FF_API_AVCODEC_CLOSE. > 3. The documentation of this field does not mention ownership, but given > that this field existed for a long time lavc's previous behaviour > established the implicit contract that lavc will free this in > avcodec_close(). You are breaking this implicit contract for no good Yes, I wrote this set forgetting avcodec_close() was still a thing. > reason apart from this new principle that user-set stuff shared with > AVCodecParameters should not be freed in avcodec_close(). Which is crazy > given that the relevant AVCodecParameters field has only been added > recently. _______________________________________________ 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:[~2024-05-01 20:51 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-01 19:01 [FFmpeg-devel] [PATCH 1/3] avcodec/avcodec: prevent ch_layout from being uninitialized in ff_codec_close() James Almer 2024-05-01 19:01 ` [FFmpeg-devel] [PATCH 2/3] avcodec/avcodec: don't free coded_side_data in ff_codec_close() when decoding James Almer 2024-05-01 20:40 ` Andreas Rheinhardt 2024-05-01 20:51 ` James Almer [this message] 2024-05-01 19:01 ` [FFmpeg-devel] [PATCH 3/3] avcodec/avcodec: free decoded_side_data " James Almer 2024-05-01 20:43 ` Andreas Rheinhardt 2024-05-01 20:45 ` James Almer 2024-05-01 20:55 ` Andreas Rheinhardt 2024-05-01 20:26 ` [FFmpeg-devel] [PATCH 1/3] avcodec/avcodec: prevent ch_layout from being uninitialized in ff_codec_close() Andreas Rheinhardt 2024-05-01 20:53 ` James Almer
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=01946ed3-ef94-4bb3-91e9-cbcc81c25fcc@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