Austin Eng 8a68537de2 Check buffer state is not destroyed before internally calling unmap ... Calling UnmapInternal would set the state to Unmapped, allowing the buffer to be mapped again even though it is destroyed. Bug: chromium:1388920 Change-Id: Ibb4da332bafd44a0d4900c8ea5bfbd674bbc35e0 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/111121 Kokoro: Kokoro <noreply+kokoro@google.com> Reviewed-by: Loko Kung <lokokung@google.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>		2022-11-22 13:34:06 +00:00
..
dawn	Check buffer state is not destroyed before internally calling unmap	2022-11-22 13:34:06 +00:00
tint	[ir] Testing updates.	2022-11-22 13:15:08 +00:00
Placeholder.cpp	Fix inclusive language presubmit	2022-04-19 22:25:45 +00:00