-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
layers: Stomp old values in ValidationStateTracker::Add() #3501
layers: Stomp old values in ValidationStateTracker::Add() #3501
Conversation
CI Vulkan-ValidationLayers build queued with queue ID 12002. |
CI Vulkan-ValidationLayers build # 5411 running. |
CI Vulkan-ValidationLayers build # 5411 passed. |
037aaba
to
7c1ea2f
Compare
CI Vulkan-ValidationLayers build queued with queue ID 12080. |
CI Vulkan-ValidationLayers build # 5412 running. |
Make sure we clear out any old values in the map in Add(). Since this is likely a bug in the state tracker if it happens, assert if the entry is an overwrite.
7c1ea2f
to
4eeb61e
Compare
CI Vulkan-ValidationLayers build queued with queue ID 12090. |
CI Vulkan-ValidationLayers build # 5413 running. |
CI Vulkan-ValidationLayers build # 5413 passed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and found GPU-AV problem
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Make sure we clear out any old values in the map in Add().
Since this is likely a bug in the state tracker if it happens,
assert if the entry is an overwrite.