e536775b40
Currently Buffer doesn't distinguish Map request callback fired by device. For example if buffer.MapAsync(), buffer.Unmap(), and buffer.MapAsync() are called in this order before the first MapAsync() finishes the MapAsync callback provided by application for the first MapAsync() is fired when Map request callback for the first MapAsync() is fired by device although the first MapAsync callback provided by application shouldn't be fired because it is already unmapped. This commit resolves this problem by assigning MapRequestId to Map request and distinguishing the callback fired by device. Change-Id: Ic29b02d27cffb254616dc7b48a60151c39f667e2 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/113222 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Kokoro: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org> |
||
|---|---|---|
| .. | ||
| dawn | ||
| tint | ||
| Placeholder.cpp | ||