Don’t copy buffer data back to JS if unnecessary, in WebGPU backend. #7007
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Connections
Fixes a problem I mentioned in passing in #6202, making that actual bug harder to hit…
Description
Currently, the WebGPU backend unnecessarily copies all mapped ranges back from Wasm to JS memory, even if it was read-only, and even if it was not actually written. This change copies the data only if an
&mut [u8]
was actually taken.Testing
My understanding is that
wgpu
currently has no automated tests for the WebGPU backend, so I patched the change into my application and tested that it doesn’t break.Checklist
cargo fmt
.taplo format
.cargo clippy
. If applicable, add:--target wasm32-unknown-unknown
--target wasm32-unknown-emscripten
cargo xtask test
to run tests.CHANGELOG.md
. See simple instructions inside file.