Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2021.1.0a7
Issue ID
1293565
Regression
Yes
[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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a9.1589