Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: sfan5 <sfan5@live.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/mediacodecdec: call MediaCodec.stop on close
Date: Thu, 8 Aug 2024 20:14:16 +0200
Message-ID: <DU0PR03MB9567EFFE226E105D1673DEB8ECB92@DU0PR03MB9567.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <tencent_4850B89696224D642007CD854F8E5502A707@qq.com>

Am 08.08.24 um 17:29 schrieb Zhao Zhili:
>> On Aug 8, 2024, at 00:27, sfan5<sfan5@live.de>  wrote:
>>
>> Hi all,
>>
>> attached is a small fix for the MediaCodec code. Tested on Android 14.
>>
>> This can free up vital resources in case of using multiple
>> decoding instances and there are buffer references left over
>> and not immediately cleaned up.
>>
>> Signed-off-by: sfan5<sfan5@live.de>
>> ---
>>   libavcodec/mediacodecdec_common.c | 12 ++++++++++++
>>   1 file changed, 12 insertions(+)
>>
>> diff --git a/libavcodec/mediacodecdec_common.c b/libavcodec/mediacodecdec_common.c
>> index d6f91e6e89..c888dea8cf 100644
>> --- a/libavcodec/mediacodecdec_common.c
>> +++ b/libavcodec/mediacodecdec_common.c
>> @@ -841,6 +841,18 @@ int ff_mediacodec_dec_flush(AVCodecContext *avctx, MediaCodecDecContext *s)
>>   
>>   int ff_mediacodec_dec_close(AVCodecContext *avctx, MediaCodecDecContext *s)
>>   {
>> +    if (!s)
>> +        return 0;
>> +
>> +    if (s->codec) {
>> +        if (atomic_load(&s->hw_buffer_count) == 0) {
>> +            ff_AMediaCodec_stop(s->codec);
>> +            av_log(avctx, AV_LOG_DEBUG, "MediaCodec %p stopped\n", s->codec);
>> +        } else {
>> +            av_log(avctx, AV_LOG_DEBUG, "Not stopping MediaCodec (there are buffers pending)\n");
>> +        }
>> +    }
>> +
> Could you elaborate on how this resolved the issue?
> If hw_buffer_count is zero, isn’t MediaCodecDecContext will be released immediately?
> If hw_buffer_count isn’t zero, the patch make no real change, so how does this patch work?

Sure.

here's the original report: 
https://github.com/mpv-android/mpv-android/issues/966

summary:

mpv's hwdec code uses a single surface to facilitate zero-copy video 
playback. Keeping an active MediaCodec instance connected to the surface 
blocks the same surface from being used with a different MediaCodec 
instance.

However mpv also keeps a reference to the last rendered frame alive even 
when switching between files. It also flushes the codec when it's done 
with a file. This leads to a situation where hw_buffer_count == 0 && 
refcount > 1.

If you were to say that this should be fixed in mpv I would agree and I 
have indeed proposed a PR for this. But I noticed we're never calling 
stop() in mediacodecdec and it's a very simple remedy.
_______________________________________________
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".

  reply	other threads:[~2024-08-08 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 16:27 sfan5
2024-08-07 19:11 ` Matthieu Bouron
2024-08-08 15:29 ` Zhao Zhili
2024-08-08 18:14   ` sfan5 [this message]
2024-08-09  2:17     ` Zhao Zhili

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=DU0PR03MB9567EFFE226E105D1673DEB8ECB92@DU0PR03MB9567.eurprd03.prod.outlook.com \
    --to=sfan5@live.de \
    --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