Search Issue Tracker
Fixed in 2020.2.X
Votes
3
Found in
2020.2.3f1
Issue ID
1312591
Regression
Yes
[Vulkan] Crash on vk::ImageManager::RemoveTextureIDBinding when exiting Editor
How to reproduce:
1. Open the project from "DOTSEntitiesVulkan.zip"
2. Close Editor
Reproducible with: 2020.2.3f1, 2020.2.4f1
Not reproducible with: 2018.4.31f1, 2019.4.20f1, 2020.2.2f1, 2021.1.0b5, 2021.2.0a4
First lines of stack trace:
0x00007ff7c0aa4bce (Unity) vk::ImageManager::RemoveTextureIDBinding
0x00007ff7c0a4ff3e (Unity) vk::Image::~Image
0x00007ff7c0a52084 (Unity) vk::Image::`vector deleting destructor'
0x00007ff7c0a55df3 (Unity) vk::ResourceDestructionStagingArea::Clear
0x00007ff7c0a4f666 (Unity) GfxDeviceVK::~GfxDeviceVK
0x00007ff7c0a52004 (Unity) GfxDeviceVK::`vector deleting destructor'
Note:
1. Reproducible with Vulkan
2. Not reproducible with DirectX11, DirectX12
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
- Shader Graph validation errors are not pointing to the right implementation
Resolution Note (fix version 2020.2):
Fixed in 2020.2.5f1
Resolution Note (fix version 2020.2):
Fixed in 2020.2.5f1