This is an automated email from the git hooks/post-receive script. Git pushed a commit to branch release/9.0 in repository ffmpeg.
commit 6758e66fb5272fd46d3454d2b7b3a4195037a4a3 Author: Lynne <[email protected]> AuthorDate: Sun Jul 5 16:30:10 2026 +0900 Commit: Lynne <[email protected]> CommitDate: Sun Jul 12 13:47:24 2026 +0900 ffv1enc_vulkan: fix VRAM size detection The reduction accumulated into the zero-initialized context field instead of the local variable, so the detected VRAM was whatever device-local heap the implementation listed last, usually the 256MiB BAR heap rather than the multi-GiB VRAM heap. This made the encoder take the host-memory fallback (or fail the allocation outright at 12K and above) on hardware with plenty of VRAM. (cherry picked from commit 43d0d365f3bb4ca9f6e5e6615a4f7aecc6e9df9d) --- libavcodec/ffv1enc_vulkan.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/ffv1enc_vulkan.c b/libavcodec/ffv1enc_vulkan.c index 2c83e6869e..fdbe63efa9 100644 --- a/libavcodec/ffv1enc_vulkan.c +++ b/libavcodec/ffv1enc_vulkan.c @@ -1376,7 +1376,7 @@ static av_cold int vulkan_encode_ffv1_init(AVCodecContext *avctx) max_host_size = 0; for (int i = 0; i < fv->s.mprops.memoryHeapCount; i++) { if (fv->s.mprops.memoryHeaps[i].flags & VK_MEMORY_HEAP_DEVICE_LOCAL_BIT) - max_heap_size = FFMAX(fv->max_heap_size, + max_heap_size = FFMAX(max_heap_size, fv->s.mprops.memoryHeaps[i].size); if (!(fv->s.mprops.memoryHeaps[i].flags & VK_MEMORY_HEAP_DEVICE_LOCAL_BIT)) max_host_size = FFMAX(max_host_size, _______________________________________________ ffmpeg-cvslog mailing list -- [email protected] To unsubscribe send an email to [email protected]
