Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a1
2020.1.0a13
Issue ID
1197292
Regression
Yes
[Vulkan][AMD] Editor crashes with vkDestroyDescriptor Pool when changing API to Vulkan
Editor crashes with vkDestroyDescriptor Pool when changing API to Vulkan
1. Create a new Project
2. Open Player Settings
3. Change Graphics API to Vulkan
4. Click on Restart editor button
Expected Result:
Editor restarts with updated Graphics API
Actual Result:
Editor crashes at the time of restarting
Reproducible on: 2020.1.0a13, 2020.1.0a12, 2019.3.0b10, 2019.3.0a1
Working fine on: 2019.2.12f1
Environment : Windows 10 only
Note:
- This issue is occurring with AMD Radeon R9 200 Series Graphics card
- Project cant be opened after this scenario
- Attaching Graphics card details
- Similar bug was reported but stack trace was different : https://fogbugz.unity3d.com/f/cases/1112150/
========== OUTPUTTING STACK TRACE ==================
0x00007FFB7801D608 (vulkan-1) vkDestroyDescriptorPool
0x00007FF7A6A7CAD3 (Unity) GfxDeviceVK::GfxDeviceVK
0x00007FF7A6A88E1A (Unity) CreateVKGfxDevice
0x00007FF7A7A928C2 (Unity) CreateRealGfxDevice
0x00007FF7A6A01C10 (Unity) CreateClientGfxDevice
0x00007FF7A7A92203 (Unity) CreateGfxDevice
0x00007FF7A7A9400F (Unity) InitializeGfxDevice
0x00007FF7A7505F44 (Unity) InitializeEngineGraphics
0x00007FF7A88836BD (Unity) Application::InitializeProject
0x00007FF7A9078EB5 (Unity) WinMain
0x00007FF7AA6E88F6 (Unity) __scrt_common_main_seh
0x00007FFBD5347BD4 (KERNEL32) BaseThreadInitThunk
0x00007FFBD6D0CED1 (ntdll) RtlUserThreadStart
========== END OF STACKTRACE ===========
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment