36cd17488a
The server didn't take intercept the destroy() call which meant the buffer could be unmapped by dawn_native without the status updated in ServerBuffer. This caused crash when a subsequent UpdateMappedData command was handled and tried to write into the mapped buffer. The client needs to also track destroy() otherwise it could sent an UpdateMappedData to a destroyed buffer which is a fatal error. Tests are added that cover the client-server interaction for this, but the pattern that the following is unfortunately not tested directly against the wire server: - CreateBufferMapped - Destroy - UpdateMappedData Bug: chromium:1068466 Change-Id: If5185d4a8a81cd5f6bb41c9888a18c44c14b2de4 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/18961 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> |
||
---|---|---|
.. | ||
common | ||
dawn | ||
dawn_native | ||
dawn_platform | ||
dawn_wire | ||
fuzzers | ||
include | ||
tests | ||
utils | ||
Dummy.cpp |