aboutsummaryrefslogtreecommitdiff
path: root/layers/core_validation.cpp
diff options
context:
space:
mode:
authorChris Forbes <chrisforbes@google.com>2017-08-01 17:19:52 -0700
committerChris Forbes <chrisf@ijw.co.nz>2017-08-02 09:19:35 -0700
commita1b8c48bfb5ccbb6760e0b34fac5d80768bb4dfe (patch)
tree4b4ffd3443e33eb4bd254e47056558735c2dbeae /layers/core_validation.cpp
parent4916086cf41ff0c5137d81fe251af8b1c4f30c24 (diff)
downloadusermoji-a1b8c48bfb5ccbb6760e0b34fac5d80768bb4dfe.tar.xz
layers: Don't do bogus transitions in invalidateCommandBuffers
Total nonsense like: RECORDING -> INVALID_INCOMPLETE -> INVALID_COMPLETE was possible when there were two invalidations.
Diffstat (limited to 'layers/core_validation.cpp')
-rw-r--r--layers/core_validation.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/layers/core_validation.cpp b/layers/core_validation.cpp
index 172cdbf0..eaadcbf7 100644
--- a/layers/core_validation.cpp
+++ b/layers/core_validation.cpp
@@ -4117,7 +4117,7 @@ void invalidateCommandBuffers(const layer_data *dev_data, std::unordered_set<GLO
"Invalidating a command buffer that's currently being recorded: 0x%p.", cb_node->commandBuffer);
cb_node->state = CB_INVALID_INCOMPLETE;
}
- else {
+ else if (cb_node->state == CB_RECORDED) {
cb_node->state = CB_INVALID_COMPLETE;
}
cb_node->broken_bindings.push_back(obj);