Closed Bug 1469791 Opened Last year Closed Last year
Use longer timeout for Acquire
RenderDXGITextureHostOGL::Lock() and RenderDXGIYCbCrTextureHostOGL::Lock() use short timeout for IDXGIKeyedMutex::AcquireSync(). Another code like the following uses longer timeout. It seems better to use same timeout value. https://dxr.mozilla.org/mozilla-central/source/gfx/layers/d3d11/TextureD3D11.cpp#232 https://dxr.mozilla.org/mozilla-central/source/gfx/layers/d3d11/TextureD3D11.cpp#1870
On my old win10 laptop, I often saw the timeout error log with current 100ms timeout.
(In reply to Sotaro Ikeda [:sotaro] from comment #1) > On my old win10 laptop, I often saw the timeout error log with current 100ms > timeout. It is during youtube playback.
Attachment #8986402 - Flags: review?(nical.bugzilla)
We check device reset at RenderCompositorANGLE::BeginFrame(). Then longer device reset during Lock() should be OK.
Attachment #8986402 - Flags: review?(nical.bugzilla) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/06f179ea49cf Use longer timeout for AcquireSync() r=nical
You need to log in before you can comment on or make changes to this bug.