New issue
Advanced search Search tips

Issue 842340 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug

Blocking:
issue 827649



Sign in to add a comment

D3D11 may need a memory barrier mechanism

Project Member Reported by rkuroiwa@chromium.org, May 11 2018

Issue description

Currently D3D11VideoDecoderImpl uses a "sync token release" in order to mark a picture (D3D11PictureBuffer) as reusable.

This is probably not sufficient because the sync token is signaled once the "commands have been enqueued" and does not mean that the picture has been displayed.
https://chromium-review.googlesource.com/c/chromium/src/+/956602/14/media/gpu/windows/d3d11_video_decoder_impl.cc#319

We would probably need to set textures to be D3D11_RESOURCE_MISC_SHARED_KEYEDMUTEX or use fences.
 
Blocking: 827649
Cc: tmathmeyer@chromium.org liber...@chromium.org
Owner: ----
Status: Available (was: Untriaged)
un-assigning since i'm not working on this currently.

Sign in to add a comment