Improve synchronization of rendering after changes from transfer queues. #98388
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.
After transfer queues were merged, some new unexpected synchronization errors popped up that were previously not encountered because the setup queue was introducing its own barriers and forcing most of the caches to be flushed through a global memory barrier.
These changes introduce proper synchronization tracking for usages on the previous frame, as the hazards were not visible inside the same frame but rather between frames. This has fixed some flickering that was visible in the TPS Demo in Mobile that did not happen before #90400 was merged.
This PR also fixes an error where debug labels were not being properly closed each frame, leading to the labels leaking into the next frames and causing them to keep growing in depth.