Fix allocator null for trim capture #1713
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Author jirongjiao not on autobuild list. Waiting for curator authorization before starting CI build. |
|
CI gfxreconstruct build queued with queue ID 256005. |
|
CI gfxreconstruct build # 4829 running. |
|
CI gfxreconstruct build # 4829 passed. |
davidd-lunarg
approved these changes
Sep 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
During trim capture of some D3D12 apps, some command allocators may be released during state tracking stage, resulting trace replay crash at CreateCommandList() due to null command allocator.
Solution
Create temp command allocator for CreateCommandList when it's allocator has been released during state tracking.