Fix problem that might go away with resource record shutdown order

This commit is contained in:
baldurk
2015-09-16 11:17:17 +02:00
parent 3b3053369c
commit e5e8fa29f5
2 changed files with 7 additions and 4 deletions
+4 -1
View File
@@ -52,7 +52,10 @@ class VulkanResourceManager : public ResourceManager<VkResource, VkResourceRecor
{
while(!m_VkResourceRecords.empty())
{
auto it = m_VkResourceRecords.begin();
// VKTODOLOW we pick from the end, on the assumption that in
// namespace order (which is resource record order), later entries
// always have parents that are earlier.
auto it = --(m_VkResourceRecords.end());
ResourceId id = it->second->GetResourceID();
it->second->Delete(this);
+3 -3
View File
@@ -44,15 +44,15 @@ enum VkNamespace
eResAttachmentView,
eResFramebuffer,
eResRenderPass,
eResShader,
eResShaderModule,
eResPipeline,
eResShader,
eResPipelineCache,
eResPipelineLayout,
eResPipeline,
eResSampler,
eResDescriptorSet,
eResDescriptorPool,
eResDescriptorSetLayout,
eResDescriptorSet,
eResViewportState,
eResRasterState,
eResMSAAState,