Aug. 5, 2026
12:26 p.m.
On Sun Aug 2 15:26:11 2026 +0000, Giovanni Mascellani wrote:
Do you understand why that's happening? It's unexpected to me, according to what I remember of this API. I believe it is a mistake in the windows implementation of the d3d12-backed buffer. Running the test with d3d12 validation layers enabled points to d3d12 API misuse specifically with read-write locking, while just read locking or just write locking works as expected. I've found it easier to explicitly test for the error code instead of working around it.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/11420#note_148010