WebGPURenderer: Fix getArrayBufferAsync race condition and ensure proper buffer sequencing #29293
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.
Fixed #29270
WebGL Errors:
performance warning: READ-usage buffer was read back without waiting on a fence. This caused a graphics pipeline stall.
GL_INVALID_OPERATION: A transform feedback buffer that would be written to is also bound to a non-transform-feedback target
WebGPU Error:
Failed to execute 'mapAsync' on 'GPUBuffer': Buffer was unmapped before mapping was resolved.
Description
Resolved #29270 by re-binding immediately after the fencing operation and correctly unbinding buffers post-operation in the WebGL backend.
Additionally, removed the readBufferGPU caching system in the WebGPU backend, which could cause race conditions during stress tests on subsequent calls.
This contribution is funded by Segments.AI & Utsubo