Search Issue Tracker

Fixed in 2020.2

Votes

1

Found in

2020.2.2f1

Issue ID

1309519

Regression

Yes

[Vulkan] Crash in Windows Standalone when Vulkan is set as rendering API and player window is out of focus

Vulkan

-

Repro:
- download this small project (Party.zip)
- Make sure the Main scene is in the build settings and that Vulkan is set as the rendering API
- build player for Desktop, Win64 standalone
- Run the executable, make sure the scene renders and then press the Windows Key (or do anything that takes the renderer out of focus)
- notice the crash

Reproduces on: 2020.2.sf1, 2020.2.3f1
Does not reproduce on: 2020.2.1f1 2021.1.0b4, 2019.4.18f1

stack treace:
========== OUTPUTTING STACK TRACE ==================
0x00007FF8EE785F40 (amdvlk64) vk_icdGetInstanceProcAddrSG
0x00007FF8EE7AEDD1 (amdvlk64) vk_icdGetInstanceProcAddrSG
0x00007FF8EE7AE8C5 (amdvlk64) vk_icdGetInstanceProcAddrSG
0x00007FF8EE83005D (amdvlk64) vk_icdGetInstanceProcAddrSG
0x00007FF8EE7B5D07 (amdvlk64) vk_icdGetInstanceProcAddrSG
0x00007FF8EE53EE1D (amdvlk64) vk_icdNegotiateLoaderICDInterfaceVersion
0x00007FF8EE53E60E (amdvlk64) vk_icdNegotiateLoaderICDInterfaceVersion
0x00007FF8EE54288A (amdvlk64) vk_icdNegotiateLoaderICDInterfaceVersion
0x00007FF6E2DC2B91 (Unity) vk::PipelineBarrierMap::Submit
0x00007FF6E2DCA526 (Unity) vk::CommandBuffer::FlushBarriers
0x00007FF6E2DC6591 (Unity) vk::CommandBuffer::ClearColor
0x00007FF6E2D953DE (Unity) vk::Image::Clear
0x00007FF6E2DC82D5 (Unity) vk::RenderSurface::CreateColorSurfaceImpl
0x00007FF6E2DC8484 (Unity) vk::RenderSurface::CreateColorSurfacePlatform
0x00007FF6E2D98594 (Unity) GfxDeviceVK::CreateColorRenderSurfacePlatform
0x00007FF6E617B918 (Unity) GfxDeviceWorker::RunCommand
0x00007FF6E618832C (Unity) GfxDeviceWorker::RunExt
0x00007FF6E6188878 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF6E3BF6135 (Unity) Thread::RunThreadWrapper
0x00007FF96EDF7C24 (KERNEL32) BaseThreadInitThunk
0x00007FF96F40D4D1 (ntdll) RtlUserThreadStart
========== END OF STACKTRACE ===========
A crash has been intercepted by the crash handler. For call stack and other details, see the latest crash report generated in: C:/Users/CATALI~1/AppData/Local/Temp/Unity/Editor/Crashes
Stack trace:
0x00007ff626454bce (Unity) vk::ImageManager::RemoveTextureIDBinding
0x00007ff6263fff3e (Unity) vk::Image::~Image
0x00007ff626402084 (Unity) vk::Image::`vector deleting destructor'
0x00007ff626405df3 (Unity) vk::ResourceDestructionStagingArea::Clear
0x00007ff6263ff666 (Unity) GfxDeviceVK::~GfxDeviceVK
0x00007ff626402004 (Unity) GfxDeviceVK::`vector deleting destructor'
0x00007ff62739849c (Unity) DestroyRealGfxDevice
0x00007ff6297f4956 (Unity) GfxDeviceWorker::~GfxDeviceWorker
0x00007ff6297f4ab4 (Unity) GfxDeviceWorker::`vector deleting destructor'
0x00007ff6263884a8 (Unity) GfxDeviceClient::~GfxDeviceClient
0x00007ff626388844 (Unity) GfxDeviceClient::`vector deleting destructor'
0x00007ff6273983d6 (Unity) DestroyGfxDevice
0x00007ff628ab878e (Unity) WinMain
0x00007ff62a91e3c6 (Unity) __scrt_common_main_seh
0x00007ff96edf7c24 (KERNEL32) BaseThreadInitThunk
0x00007ff96f40d4d1 (ntdll) RtlUserThreadStart

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.