Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.2f1
Issue ID
UUM-8522
Regression
Yes
[Backport] [Vulkan] Editor crashes on vk::ImageManager::RemoveTextureIDBinding on changing Graphics APIs to OpenGLCore
-Editor crashes on vk::ImageManager::RemoveTextureIDBinding on changing Graphics APIs from Vulkan to OpenGLCore.
-Crash window appears, Bug Reporter opens up, and then Editor opens up.
Steps to repro:
1. Create a new project.
2. File > Build Settings > Player Settings > Other Settings.
3. Uncheck "Auto Graphics APIs for Windows" checkbox.
4. Add Vulkan > Drag to the Top of the list > Restart.
5. Add OpneGLCore > Drag to the Top of the list > Restart.
Actual Result:
Crash window appears, Bug Reporter opens up, and then Editor opens up.
Expected Result:
Graphics APIs should change to OpenGLCore without opening crash window and Bug Reporter.
Reproducible in:
2021.1.0a7.
Working Fine in:
2021.1.0a6, 2020.2.0b12.
Environment:
Occurring only on Windows.
Stacktrace:
Stack trace:
0x00007ff6dcad098e (Unity) vk::ImageManager::RemoveTextureIDBinding
0x00007ff6dca85a9f (Unity) vk::Image::~Image
0x00007ff6dca87bc4 (Unity) vk::Image::`vector deleting destructor'
0x00007ff6dca97655 (Unity) vk::ResourceDestructionStagingArea::GarbageCollect
0x00007ff6dca9712a (Unity) GfxDeviceVK::FlushPools_Internal
0x00007ff6dca970ca (Unity) GfxDeviceVK::FlushPools
0x00007ff6dca85166 (Unity) GfxDeviceVK::~GfxDeviceVK
0x00007ff6dca87b44 (Unity) GfxDeviceVK::`vector deleting destructor'
0x00007ff6dd0ff55c (Unity) DestroyRealGfxDevice
0x00007ff6de962016 (Unity) GfxDeviceWorker::~GfxDeviceWorker
0x00007ff6de962174 (Unity) GfxDeviceWorker::`vector deleting destructor'
0x00007ff6dca21468 (Unity) GfxDeviceClient::~GfxDeviceClient
0x00007ff6dca216d4 (Unity) GfxDeviceClient::`vector deleting destructor'
0x00007ff6dd0ff496 (Unity) DestroyGfxDevice
0x00007ff6dda9ec80 (Unity) WinMain
0x00007ff6df652582 (Unity) __scrt_common_main_seh
0x00007ff9a1377034 (KERNEL32) BaseThreadInitThunk
0x00007ff9a183cec1 (ntdll) RtlUserThreadStart
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:
There are no fixes planned for this Bug
Resolution Note (2020.3.X):
This is already fixed in 2020.3