关于CopyResource异步性及共享资源读写一致性的技术咨询

Great question—let's unpack how CopyResource works, why you ran into that Sleep quirk with desktop duplication, and confirm whether your loop will reliably get the updated frame every time.

First, let's clarify the core behavior of CopyResource:

• This function doesn’t execute the copy immediately. Instead, it adds a copy command to the Direct3D device’s command queue, which the GPU processes in sequence. That’s the "asynchronous" behavior you’re noticing.
• The critical relief here: Direct3D automatically handles synchronization for resource dependencies. If a subsequent operation (like your WinB_RenderTexture) needs to read from pDstResource_shared, the GPU will wait until all prior write operations to that resource (including the CopyResource) are fully completed before executing the read.

Let’s walk through your loop step by step to confirm reliability: #

1. WinA_Clear(black_color): Clears WinA’s render target.
2. WinA_DrawRedTriangleOnTexture(pSrcResource): Writes the triangle to pSrcResource—this command is queued and executed in order.
3. WinA_CopyResource(pDstResource_shared, pSrcResource): Queues a copy from pSrcResource to the shared pDstResource_shared.
4. WinB_Clear(white_color): Clears WinB’s render target (no dependency on the shared resource, so this can run in parallel if the GPU allows).
5. WinB_RenderTexture(pDstResource_shared): Attempts to read the shared resource. Direct3D will block this operation (at the GPU level) until the CopyResource command from step 3 finishes. You will always get the newly rendered red triangle here, not the old black color.

Why did you need Sleep with IDXGIOutputDuplication::AcquireNextFrame? #

That’s a specific edge case with desktop duplication, not a general CopyResource issue:

• When you call AcquireNextFrame, you get a handle to the latest desktop frame, but the GPU might still be writing pixel data to that frame resource. The Sleep was a brute-force way to wait for that write to finish before calling CopyResource.
• A more reliable approach here is to use GPU fences (ID3D11Fence) to explicitly wait until the frame resource is ready for copying, instead of relying on arbitrary Sleep delays. This avoids both wasted time (sleeping longer than needed) and race conditions (sleeping too short).

Key Takeaways #

• You don’t need to manually sync CopyResource with subsequent reads—Direct3D’s implicit dependency tracking ensures the copy completes before the resource is accessed.
• Shared resources across devices/windows are handled by DXGI’s built-in synchronization, so cross-process/window access will also respect command order.
• The Sleep workaround was specific to desktop duplication’s frame acquisition, not a flaw in CopyResource itself.

内容的提问来源于stack exchange，提问作者fredirty2017