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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2020.2):
Fixed in 2020.2.5f1
Resolution Note (fix version 2020.2):
Fixed in 2020.2.5f1