From: Roman Arzumanyan <r.arzumanyan@visionlabs.ai>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>,
Timo Rothenpieler <timo@rothenpieler.org>
Subject: [FFmpeg-devel] [PATCH] libavutil/hwcontext_cuda: fix bug in cuda_device_uninit
Date: Fri, 29 Sep 2023 15:48:12 +0300
Message-ID: <CAJZRZVnnfcWLogODuX0R_SisHaWVEFvnvkZ3f+pFo0uzjqUVHw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
Hello,
In my previous patch which introduced the AV_CUDA_USE_CURRENT_CONTEXT
feature I unintentionally made a mistake of not checking this flag when
uninitializing the CUDA.
It was causing cuda_device_uninit() function to destroy the CUDA context it
didn't create.
So far it only reproduces under cuda compute sanitizer:
========= COMPUTE-SANITIZER
========= Program hit invalid device context (error 201) on CUDA API call
to cuCtxDestroy_v2.
But nonetheless shall be fixed. Please find a fix in attached file, now
cuCtxDestroy is called under condition.
[-- Attachment #2: 0001-libavutil-hwcontext_cuda-fix-cuda_device_uninit-when.patch --]
[-- Type: application/octet-stream, Size: 1051 bytes --]
[-- Attachment #3: 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".
reply other threads:[~2023-09-29 12:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJZRZVnnfcWLogODuX0R_SisHaWVEFvnvkZ3f+pFo0uzjqUVHw@mail.gmail.com \
--to=r.arzumanyan@visionlabs.ai \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=timo@rothenpieler.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